Online 172.240.229.155:28055 checked 8m ago
Bilgewater Springs
Connect
srv = rust.server("172.240.229.155:28056")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:35 UTC FW26d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
4500 · seed 966022937
- map
- Procedural Map
- size
- 4500
- seed
- 966022937
Server
srv.info()- address
- 172.240.229.155:28055
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:35 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 91/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 93/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 37/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 14/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Bilgewater Springs rank?
Player hours over seven days put Bilgewater Springs at #15,419, in the top 69% of the ranked set.
How many players does Bilgewater Springs hold at once?
Bilgewater Springs reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.
About the server
How well does Bilgewater Springs perform?
Averaged over 48 hours: 59 server fps, never under 56. The entity count peaked at 112,262, covering buildings, deployables and the rest of the world. Memory peaked at 3,266 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Bilgewater Springs on?
Rust network protocol 2634 and build 166494 on Windows is what Bilgewater Springs runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Bilgewater Springs, and is it online now?
Bilgewater Springs reports itself online at the current refresh. Count back 22 hours from its reported uptime to get the last restart. 157 of 168 hours up over the last 7 full days, or 93%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Bilgewater Springs run from?
There is no region published for Bilgewater Springs. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 172.240.229.155:28055.
Rules, settings, map
Which settings and rules does Bilgewater Springs run?
You will not find a gather rate in the string Bilgewater Springs. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Bilgewater Springs loaded?
Bilgewater Springs runs a procedural map of size 4,500 with seed 966022937, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Bilgewater Springs wipe, and on what schedule?
Once a month Bilgewater Springs wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 26 days 8 hours ago.
On Bilgewater Springs, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 23 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain Bilgewater Springs?
The Rust Data lists that Bilgewater Springs fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Bilgewater Springs?
These tags are published by Bilgewater Springs and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Bilgewater Springs?
Enter client.connect 172.240.229.155:28055 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.