Skip to the page
Network live 11,689 servers online 59,961 players aboard 106 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Bilgewater Springs

Online 172.240.229.155:28055 checked 7m ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 26d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 8d 8h · high confidence
0/ 50 players now 0% full
07-day averagepeak –
#15,411ranktop 69%
26d agolast wipeno schedule published
8d 8hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

AveragePeak
0123411:0020:0005:0015:0000:0009:00

Hourly average and peak, UTC.

Server performance

02040608011:0020:0005:0015:0000:0009:00

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 8d 8h.

The force wipe · high confidence
1wipe-day peakplayers, last three wipes

Coming wipes

  1. 8d 8hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 36d 8hThu 3 Dec, 19:00 UTC19:00 UKFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.

Wipes

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 8d 8h
    Next wipe expected · the force wipe
  2. Thu 1 Oct, 22:35 UTC FW 23:35 UK · 26d ago
    Force wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 155 on average 171 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average 124 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average 186 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average 136 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average 14 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average 53 / 1000
Help desk

Quick answers

From the figures on this page.

Player count

How does Bilgewater Springs compare with other Rust servers in the rankings?

Over the past seven days, Bilgewater Springs has climbed to #15,411 for player hours, putting it in the top 69% of all ranked servers.

What is the current population on Bilgewater Springs?

The current count is 0 players on 50 slots for Bilgewater Springs. For the last seven days the average player count was 0.

Map and rules

On what map does Bilgewater Springs take place?

Generated by the game with seed 966022937, the procedural map on Bilgewater Springs is size 4,500. Size and seed match means the map matches, so you can view it on RustMaps from this page.

Which settings and rules apply on Bilgewater Springs?

The name of Bilgewater Springs gives no gather rate. The game's default applies: 8 players to a group at most. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Plugins come from Oxide. The VAC anti-cheat from Valve is enabled.

About the server

What is the location of Bilgewater Springs?

There is no region published for Bilgewater Springs. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. The address to connect to is 172.240.229.155:28055.

Does Bilgewater Springs perform well?

The 48-hour average for server fps stands at 58, never dipping below 22. The world held as many as 112,262 entities: buildings, deployables and the rest. The highest memory reading was 3,266 MB. Lag, to players, means low fps alongside an entity count on the rise.

Is Bilgewater Springs up, and how good is its uptime?

Right now, Bilgewater Springs is online. About 2 hours ago is when it last restarted, judged by the uptime it gives. 93% is the uptime for the last 7 full days, up for 157 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 13 September 2026.

On what Rust version does Bilgewater Springs operate?

The version on Bilgewater Springs is Rust network protocol 2634 and build 166494, running on Windows. The same protocol is required to join, and Steam takes care of updating it.

Wipe times

What should you expect from wipe day on Bilgewater Springs?

The average busiest point of its recent wipes was 1 players. After 23 hours the latest wipe's crowd hit its peak.

On what schedule does Bilgewater Springs reset its map?

The only wipe Bilgewater Springs takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC comes its next wipe, the force wipe that every Rust server shares. The world it is running was made 26 days 12 hours.

Tags and listings

On Rust Wipe Tracker, which lists and filters is Bilgewater Springs part of?

These Rust Wipe Tracker lists take Bilgewater Springs: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What is the meaning of the server tags on Bilgewater Springs?

The game's server browser picks up these Bilgewater Springs tags: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team, which is the default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

What is the process to join Bilgewater Springs?

Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 172.240.229.155:28055.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team, which is the default.
v2634
Protocol Join only if your game runs protocol 2634.
cs166494
Build The game build is 166494.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code The region code is unset.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.