Rust Data LabData lab · live
Live readings Servers11,765 Players63,710 Populated3,546 Fresh wipes · 3h133 Sampled every 5 min

Element card · group Modded · atomic number 15,404, its rank

Bilgewater Springs

Online 172.240.229.155:28055 checked 8m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak –
Rank · atomic number#15,404top 69%
Last wipe26d agono schedule published
Next wipe8d 20hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
02040608023:0008:0017:0003:0012:0021: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Reaction kinetics

Wipe schedule

force wipes only

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

wipe-day peak1players, last three wipes

Coming wipes

  1. 8d 20hThu 5 Nov, 19:00 UTCFW
  2. 36d 20hThu 3 Dec, 19:00 UTCFW

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.

Reaction log

Wipes

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

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 85
    ShockRust | Blue | NoLimit no group limit · 164 on average 85/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 129
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 129/ 100
  3. 3 Re RETRO RUST #1 … 96
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 112 on average 96/ 225
  4. 4 Ru RustSpain.com … 33
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 33/ 200
  5. 5 Ru 404 RUST 2Х|ДЛ… 89
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 86 on average 89/ 700
  6. 6 Ru 404 RUST 2Х|ДЛ… 25
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 25/ 1,000

Quick answers

from the figures on this page

Server setup

What map is in play on Bilgewater Springs?

Bilgewater Springs runs a procedural map of size 4,500 with seed 966022937; the game generates it. You can view it on RustMaps from this page, since matching size and seed produce the same map.

How is Bilgewater Springs configured, and what rules apply?

The name of Bilgewater Springs carries no gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Oxide. VAC is on, Valve's anti-cheat.

About the server

Which location is Bilgewater Springs based in?

There is no region on record for Bilgewater Springs. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. Connect at 172.240.229.155:28055.

Which Rust version is Bilgewater Springs on?

Rust network protocol 2634 and build 166494 on Windows is what Bilgewater Springs uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does Bilgewater Springs stay online?

At the moment, Bilgewater Springs is online. About 14 hours ago is when it last restarted, based on its uptime. For the last 7 full days, 157 of 168 hours were online, giving 93% uptime. It first appeared to Rust Data Lab on 13 September 2026.

Does Bilgewater Springs hold a steady performance?

In the last 48 hours, it averaged 59 server fps, with a low of 56. The entity count reached 112,262, including buildings, deployables and all other world items. Up to 3,501 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Wipe schedule

What is the wiping pattern on Bilgewater Springs?

Once a month is all Bilgewater Springs wipes, with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is when this server next wipes, along with every other Rust server. 26 days ago the current world was made.

How does Bilgewater Springs look on the day of a wipe?

At their busiest, recent wipes averaged 1 players. The latest wipe's peak fell 23 hours after it began.

Tags, lists

Which meanings sit behind the tags on Bilgewater Springs?

The game's server browser reads the tags Bilgewater Springs publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 is the slot count; ts8 (Group limit): 8 per team, the default the game ships with; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166494 (Build): It runs build 166494; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): A region code has not been set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Which Rust Data Lab filters and lists does Bilgewater Springs appear in?

The Rust Data Lab lists that include Bilgewater Springs are: Modded Rust servers, measured. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Against other Rust servers, where does Bilgewater Springs place?

The seven-day player-hours table has Bilgewater Springs at #15,404, in the top 69% of ranked servers.

What does the current player count on Bilgewater Springs tell you?

Bilgewater Springs currently shows 0 players across 50 slots. The past week gives an average of 0 players.

How to join

What steps get you onto Bilgewater Springs?

You can connect by pressing F1 in Rust and entering client.connect 172.240.229.155:28055, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what 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 slot count.
ts8
Group limit 8 per team, the default the game ships with.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166494
Build It runs build 166494.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code A region code has not been set here.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under 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.