Station XX-15409 · recording
Bilgewater Springs
Online 172.240.229.155:28055 checked 12m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,409
- top 69%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 8d 18h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 18h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 8d 18hThu 5 Nov, 19:00 UTCFW
- 36d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 22:35 UTC FW26d ago | M0.0▲rising | 1 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on Bilgewater Springs?
The procedural map on Bilgewater Springs is size 4,500 with seed 966022937, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Bilgewater Springs?
No gather rate appears in the name of Bilgewater Springs. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Bilgewater Springs right now?
At this moment, Bilgewater Springs records 0 players across 50 slots. The seven-day average for this server is 0 players.
How does Bilgewater Springs rank against other Rust servers?
On player hours for the past week, Bilgewater Springs sits at #15,409, which puts it inside the top 69% of every ranked server.
Server details
How reliably does Bilgewater Springs stay online?
As recorded now, Bilgewater Springs is running. Going by the uptime figure it reports, it restarted about 16 hours ago. 133 of 168 hours in the last 7 full days were up time, 79% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does Bilgewater Springs hold a steady tick rate?
Its average server fps over the last 48 hours was 59, and it never dropped below 56. Buildings, deployables and all the rest of the world's entities brought it to a high of 112,262. Memory use peaked at 3,501 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is Bilgewater Springs hosted?
Nothing about a region comes from Bilgewater Springs. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 172.240.229.155:28055.
Which Rust version is Bilgewater Springs running?
Bilgewater Springs is running Rust network protocol 2634 and build 166494 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Bilgewater Springs?
On average, the busiest point of its recent wipes drew 1 players. 23 hours into the latest wipe, the crowd reached its peak.
How often does Bilgewater Springs wipe, and on which days?
At the force wipe each month Bilgewater Springs wipes, and at no other time. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 26 days 1 hours.
Server tags
What do the server tags on Bilgewater Springs mean?
These are the tags Bilgewater Springs publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): It runs game build 166494; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Bilgewater Springs appear?
You will find Bilgewater Springs on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to Bilgewater Springs?
You can connect by pressing F1 in Rust and typing client.connect 172.240.229.155:28055 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.