Bilgewater Springs
Online 172.240.229.155:28055 checked 9m ago
Server instruments
last reading Wed 10:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 22 · below 20 is lag, below 10 is badEntities
48 h range 89,228–112,262 · memory 2,626 MBUptime
3 h 1 min since its last restart, at the last readingPlayers
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 7h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC8d 7hFW
- WPT 2Thu 3 Dec, 19:00 UTC36d 7hFW
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- 172/500
- 133/100
- 179/225
- 126/700
- 15/200
- 54/1000
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on Bilgewater Springs?
An average of 1 players came at the busiest on its recent wipes. 23 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does Bilgewater Springs follow?
The only wipe for Bilgewater Springs is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 26 days 12 hours ago.
Tag meanings
Which tags does Bilgewater Springs carry, and what do they mean?
These are the tags Bilgewater Springs publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Bilgewater Springs appear in Rust Metrics lists and filters?
On Rust Metrics, Bilgewater Springs sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does Bilgewater Springs hold among Rust servers?
Ranking for Bilgewater Springs: #15,411 on seven-day player hours, top 69% of all ranked servers.
How full does Bilgewater Springs get?
Current headcount on Bilgewater Springs: 0 players, 50 slots available. Check: player average. 0 over the last seven days.
Operator and location
What location is Bilgewater Springs hosted in?
No region tag on Bilgewater Springs. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 172.240.229.155:28055.
What Rust version is Bilgewater Springs on?
Rust network protocol 2634 and build 166494 on Windows is the build Bilgewater Springs runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for Bilgewater Springs?
Over the last 48 hours the average was 58 server fps; the floor was 22. Peak entity count: 112,262. Buildings, deployables and all else included. Check: memory. Peak use was 3,266 MB. What players call lag comes from low fps and an entity count on the rise.
Is Bilgewater Springs up, and how often does it stay up?
Bilgewater Springs reports online. Status: normal. Reading: uptime. About 3 hours ago it restarted, on its own count. Uptime for the last 7 full days: 157 of 168 hours, or 93%. The first sighting on Rust Metrics was 13 September 2026.
Map and rules
What settings and rules apply on Bilgewater Springs?
Check: gather rate. The name Bilgewater Springs does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Bilgewater Springs?
Size 4,500 and seed 966022937: the game generates the procedural map on Bilgewater Springs from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
What do you do to join Bilgewater Springs?
To join: start Rust, press F1 and type client.connect 172.240.229.155:28055. Or press Launch Rust here and Steam opens the game and connects you.