At press time 11,612 servers35,778 players59 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 15,420

Bilgewater Springs

Online 172.240.229.155:28055 checked 7m ago

Bilgewater Springs is a Rust server. At the last count it had 0 players of a possible 50. It stands at No. 15,420 of the ranked servers, the top 69%. It last wiped 26d ago, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as modded, oxide.

§ 1Attendance

AveragePeak
0123404:0013:0022:0008:0017:0002:00

Hourly average and peak, UTC.

§ 2Performance

02040608004:0013:0022:0008:0017:0002:00

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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

§ 4The wipe scheduleforce wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence

The rhythm
Wipe-day peak1

players, last three wipes

Coming wipes
Date, UTCHence
Thu 5 Nov, 19:00 FW8d 15h
Thu 3 Dec, 19:00 FW36d 15h

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers 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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 ShockRust | Blue | NoLimit39/500 no group limit · 160 on average
  2. 2 МИНИ-КАРТА 2Х | STORM | FPS+ 24.10121/100 EU · groups of 8+ · weekly · 128 on average
  3. 3 RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.1050/225 EU · groups of 16+ · weekly · 114 on average
  4. 4 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.1020/700 EU · groups of 16+ · monthly · 88 on average
  5. 5 RustSpain.com | EU Main5/200 EU · groups of 12+ · weekly · 87 on average
  6. 6 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.107/1000 EU · groups of 16+ · monthly · 83 on average

§ 7Questions answeredfrom the figures in this entry

Server record

The Rust version for Bilgewater Springs: which one?

The server Bilgewater Springs is on Rust network protocol 2634 and build 166494, hosted on Windows. Steam updates your game for you, and it has to be on the same protocol to join.

Is Bilgewater Springs up, and how steady is its uptime?

The records show Bilgewater Springs online at the time of this check. Of note: the reported uptime places the last restart about 19 hours ago. The records show 93% uptime over the last 7 full days: 157 of 168 hours up. Its earliest entry at Rust Server Stats is dated 13 September 2026.

How does Bilgewater Springs perform?

The records show an average of 59 server fps over 48 hours, never below 56. The entity count reached 112,262: buildings, deployables and all else in the world. Of note: memory use reached 3,501 MB. What players feel as lag: fps running low and entities climbing.

In which location does Bilgewater Springs sit?

No region appears for Bilgewater Springs. Rust Server Stats records the stated location of a server, not the location of the machine. At 172.240.229.155:28055 stands the address.

Settings and map

What map does Bilgewater Springs put players on?

Bilgewater Springs runs a procedural map, generated by the game, of size 4,500 with seed 966022937. RustMaps can display it from this page, since equal size and seed yield the same map.

What does Bilgewater Springs set down in the way of rules and settings?

No gather rate appears in the name of Bilgewater Springs. Groups are capped at 8 players, the standard default. survival is the game mode, gather, build and raid: the standard game. Combat and raiding between players are permitted. Plugins or settings change the game; it appears under Modded in the browser. Plugins run here: Oxide. VAC, Valve's anti-cheat, is enabled.

Population

What are the player numbers on Bilgewater Springs?

The record for Bilgewater Springs shows 0 players, against a capacity of 50. The record shows an average of 0 players over the past seven days.

Where does Bilgewater Springs sit in the rankings?

The seven-day player-hour table places Bilgewater Springs at #15,420, within the top 69% of ranked servers.

Tag and list record

Where does Bilgewater Springs appear among the Rust Server Stats lists and filters?

On Rust Server Stats, Bilgewater Springs is placed in these lists: Modded Rust servers. On the server list it comes up under these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings attach to the tags on Bilgewater Springs?

gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the number of slots; ts8 (Group limit): Set at the game default of 8 per team; v2634 (Protocol): Join only on protocol 2634; other versions cannot connect; cs166494 (Build): Build 166494; ptrak (Networking): RakNet carries it, the standard layer for the game; $r? (Region code): The region code is not set; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded — that is the set of tags Bilgewater Springs publishes for the game's browser. The tags include current players, queue and the time the world was made; the top of this page shows them.

The wipes

Wipe day on Bilgewater Springs: what should be expected?

Averaged over recent wipes, the crowd reached 1 at its busiest. 23 hours after the latest wipe, the crowd peaked.

On what schedule 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 shared by every Rust server. The present world dates from 26 days 5 hours.

Connection

Which steps join Bilgewater Springs?

To connect, open the console with F1 in Rust and enter client.connect 172.240.229.155:28055. The Launch Rust and join button on this page does the same through Steam.

§ 8Key to the tagswhat each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players 50 is the number of slots.
ts8
Group limit Set at the game default of 8 per team.
v2634
Protocol Join only on protocol 2634; other versions cannot connect.
cs166494
Build Build 166494.
ptrak
Networking RakNet carries it, the standard layer for the game.
$r?
Region code The region code is not set.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the browser lists it as Modded.

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.