DWG RG-S15348Server sheetchecked 9m ago
Bilgewater Springs
Online 172.240.229.155:28055 checked 9m ago
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence
Coming wipes
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 35d 21hThu 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 22:35 UTC FW26d ago | 1 | – | running | 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 servers
Quick answers
Server data
What uptime is recorded for Bilgewater Springs, and is it up?
At this moment Bilgewater Springs is online. About 12 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 157 of 168 hours up, 93% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
What does the recorded performance of Bilgewater Springs show?
59 server fps on average over the last 48 hours, and never under 22. Counted at its highest: 112,262 entities, buildings, deployables and the rest of the world included. 3,266 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.
In which location is Bilgewater Springs hosted?
No region is published by Bilgewater Springs. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 172.240.229.155:28055.
On which Rust version is Bilgewater Springs running?
Rust network protocol 2634 and build 166494 on Windows: that is what Bilgewater Springs runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
What player count is recorded on Bilgewater Springs?
Current player count on Bilgewater Springs: 0, of 50 slots. Averaged across seven days, the player count is 0.
Against other Rust servers, where is Bilgewater Springs placed?
Within the top 69% of all ranked servers: Bilgewater Springs at #15,348 for player hours, seven days recorded.
Wipe data
On Bilgewater Springs, what does the data show for wipe day?
The recent wipes averaged a busiest count of 1 players. At 23 hours after the latest wipe the crowd was at its peak.
What wipe schedule has been recorded for Bilgewater Springs?
Once a month, with the force wipe, is when Bilgewater Springs wipes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 26 days 23 hours ago the current world was made.
Map and rules
Which rules and settings are recorded for Bilgewater Springs?
No gather rate is stated in the name of Bilgewater Springs. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
What is the map for Bilgewater Springs?
Size 4,500 with seed 966022937: that is the procedural map Bilgewater Springs runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.
Filters
On Rust Graphs, which lists and filters contain Bilgewater Springs?
The Rust Graphs lists that carry Bilgewater Springs are: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
On Bilgewater Springs, what is meant by each tag?
The game's server browser reads these tags from Bilgewater Springs: gmrust (Game mode): Survival in standard Rust style; mp50 (Max players): Slots: 50; ts8 (Group limit): The default team size of 8 applies; v2634 (Protocol): Join only if your game is on protocol 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
By what method do you join Bilgewater Springs?
Connect with client.connect 172.240.229.155:28055: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z
Game
gmrust
mp50
ts8
v2634
cs166494
ptrak
$r?
Mods and access
^o
^z
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.