Bilgewater Springs
Online 172.240.229.155:28055 checked 2h 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 23h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- in 7d 23hThu 5 Nov, 19:00 UTCFW
- in 35d 23hThu 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 |
|---|---|---|---|---|
1 OCT 2026Thu 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.
Quick answers
From the figures on this page.
Rules and settings
Where can you read the rules and settings that apply on Bilgewater Springs?
The name of Bilgewater Springs does not state a gather rate. The group limit is 8 players, the game's default. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. VAC is on: Valve's anti-cheat is enabled.
What is the map on Bilgewater Springs?
Generated by the game, the procedural map of Bilgewater Springs has size 4,500 and seed 966022937. The map can be seen on RustMaps from this page, because the same size and seed give the same map.
Tags and filters
On Rust Server Index, which lists and filters carry Bilgewater Springs?
The Rust Server Index lists that include Bilgewater Springs are Modded Rust servers, filed by play style. Filed under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which tags are attached to Bilgewater Springs, and what do they stand for?
These are the tags Bilgewater Springs publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The team limit is 8, as in the standard game; v2634 (Protocol): The protocol is 2634; older or newer clients cannot join; cs166494 (Build): The game build here is 166494; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): The region code field is left empty; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Modded: the game is changed by plugins or settings. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe dates
What happens on wipe day at Bilgewater Springs?
Its recent wipes averaged 1 players at peak. 23 hours into the latest wipe, the crowd reached its peak.
When does Bilgewater Springs wipe?
The only wipe on Bilgewater Springs is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC, as the force wipe that reaches every Rust server. The world it runs now was made 26 days 20 hours.
Population
What position does Bilgewater Springs hold among Rust servers?
On player hours over seven days, Bilgewater Springs takes #15,373, within the top 69% of ranked servers.
What does the player count on Bilgewater Springs look like?
Bilgewater Springs is currently showing 0 players on 50 slots. Averaged over the last seven days, the count is 0 players.
Operator and status
What version does Bilgewater Springs use?
Rust network protocol 2634 and build 166494 on Windows is what you will find on Bilgewater Springs. To join you need the same protocol; Steam handles the update.
What is the uptime and current status of Bilgewater Springs?
Right now Bilgewater Springs is up and running. The uptime it reports puts the last restart at about 9 hours ago. It was up 157 of 168 hours across the last 7 full days, or 93% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
How well does Bilgewater Springs perform?
Averaged over the last 48 hours, server fps was 59, with a low of 22. Buildings, deployables and everything else in the world came to as many as 112,262 entities. Memory use reached as much as 3,266 MB. A climbing entity count and low fps are felt by players as lag.
What is the location of Bilgewater Springs?
No region is published by Bilgewater Springs. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. Connection details: 172.240.229.155:28055.
How to join
How can you connect to Bilgewater Springs?
Enter client.connect 172.240.229.155:28055 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
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.