LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.
Force wipe
Thursday 1 October 2026, 22:35 UTC FW
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.
The average peak across its recent wipes is 1 players. 23 hours after the latest wipe, the crowd reached its peak.
Nothing wipes Bilgewater Springs but the force wipe, once a month. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. This world dates from 26 days 4 hours.
On Rust Live Stats, Bilgewater Springs is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.
These are the tags Bilgewater Springs makes public: gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): Join only if your game is on protocol 2634; cs166494 (Build): Build: 166494; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Bilgewater Springs is carrying 0 players at the moment, with 50 slots in total. Across the past week the average was 0 players.
On player hours for the past seven days, Bilgewater Springs sits at #15,420, inside the top 69% of ranked servers.
No gather rate appears in the name Bilgewater Springs. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are in use. Anti-cheat: VAC from Valve is enabled.
A procedural map of 4,500 with seed 966022937, generated by the game, runs on Bilgewater Springs. RustMaps shows it from this page, since equal size and seed give an equal map.
There is no region from Bilgewater Springs. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 172.240.229.155:28055.
The average server fps was 59 over the last 48 hours; the lowest was 56. Buildings, deployables and everything else in the world added up to a maximum of 112,262 entities. Up to 3,501 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
Bilgewater Springs operates on Windows with Rust network protocol 2634 and build 166494. To join, your game must use the same protocol; Steam handles the update for you.
Bilgewater Springs is up and running at this moment. The uptime it reports puts the last restart at about 18 hours ago. 157 of 168 hours were online in the last 7 full days, giving 93% uptime. Rust Live Stats has tracked it since 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 172.240.229.155:28055.