Bilgewater Springs
Online 172.240.229.155:28055 checked 10m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 16h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 8d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 36d 16h | 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| 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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 161 on average | 29 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 42 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 32 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 11 / 1000 |
Quick answers
from the figures on this pageWipe data
On what cycle does Bilgewater Springs wipe?
The force wipe is the only wipe for Bilgewater Springs, once a month. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. 26 days 3 hours ago the current world was made.
Wipe day on Bilgewater Springs: what should you expect?
Across recent wipes the busiest point averaged 1 players. Peak population for the latest wipe came 23 hours after it began.
Server
What is the hosting location of Bilgewater Springs?
No region appears in what Bilgewater Springs publishes. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 172.240.229.155:28055.
What Rust build does Bilgewater Springs run?
On Windows, Bilgewater Springs runs Rust network protocol 2634 and build 166494. Your game must match the protocol to join, and Steam applies that update.
What uptime does Bilgewater Springs show, and is it up?
Bilgewater Springs reports online at the current check. The uptime it reports puts the last restart at about 17 hours ago. 93% uptime over the last 7 full days, equal to 157 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.
Is performance on Bilgewater Springs stable?
The 48-hour average was 59 server fps; the low was 56. Entity count reached 112,262, covering buildings, deployables and the rest of the world. At its highest, memory use was 3,501 MB. A climbing entity count and low fps are the lag players perceive.
Tags
What do Bilgewater Springs's tags stand for?
gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): Joining needs your game on protocol 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing, where plugins or settings change the game are the tags Bilgewater Springs publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does Bilgewater Springs appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count Bilgewater Springs among their servers: Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player numbers
Where does Bilgewater Springs sit among Rust servers?
Player hours for the last seven days place Bilgewater Springs at #15,411, in the top 69% of the ranked field.
What is the population of Bilgewater Springs?
Bilgewater Springs holds 0 players of its 50 slots as of the latest update. The seven-day mean for this server is 0 players.
Settings
How is Bilgewater Springs configured, and what rules apply?
Gather rate is not mentioned in the name of Bilgewater Springs. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.
What is the map for Bilgewater Springs?
The game generates a procedural map of size 4,500 with seed 966022937 for Bilgewater Springs. Because size and seed determine the map, it can be viewed on RustMaps via this page.
How to join
What is the way onto Bilgewater Springs?
In the Rust console (F1), enter client.connect 172.240.229.155:28055. Launch Rust on this page also works, opening Rust through Steam and connecting you.