Rust StatisticsWorking papers on every public Rust server · 58,097 players now

Bilgewater Springs

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 172.240.229.155:28055

Abstract

We describe the public Rust server Bilgewater Springs, reached at 172.240.229.155:28055. At the last check it held 0 of 50 places, against a seven-day mean of 01. It ranks #15,405 of all servers, the top 69%. It last wiped 26d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,405top 69%
Last wipe26d agono schedule published
Next wipe38d 19hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123400:0009:0018:0004:0013:0022:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
02040608000:0009:0018:0004:0013:0022:00
Figure 2: 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 8d 19h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:008d 19hforce wipefw
Thu 3 Dec, 19:0036d 19hforce wipefw
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 22:35fw26d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Bilgewater Springs
Figure 5: The map: Procedural Map, size 4500, seed 966022937. Open on RustMaps.
Table 5: The server's published settings.
Address172.240.229.155:28055
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 22:35 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4500
Seed966022937

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and predicted wipe schedule [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 163 on average63/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average129/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 113 on average75/225
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average18/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average67/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average15/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does Bilgewater Springs perform well?

Over the past 48 hours, it ran at an average of 59 server fps, with a low of 56. Its entity count reached a maximum of 112,262, including buildings, deployables and all other world objects. Its highest memory usage was 3,501 MB. When fps is low and entity count climbs, players feel lag.

A.2What is the location of Bilgewater Springs?

There is no region published for Bilgewater Springs. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 172.240.229.155:28055 is its address.

A.3How reliable is Bilgewater Springs, and is it currently online?

Bilgewater Springs is online at this time. Based on the uptime it reports, the last restart occurred about 15 hours ago. Of the 168 hours in the last 7 full days, 157 were served, an availability of 93%. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on Bilgewater Springs?

Bilgewater Springs is running Rust network protocol 2634 and build 166494 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5When are wipes carried out on Bilgewater Springs?

The only wipe for Bilgewater Springs is the monthly force wipe. This server's next wipe coincides with the force wipe on Thursday 5 November at 19:00 UTC, which affects all Rust servers. The current world has been running for 26 days.

A.6What happens on Bilgewater Springs when wipe day arrives?

Recent wipes saw an average peak of 1 players. The peak on the latest wipe came 23 hours after it began.

Population

A.7How does Bilgewater Springs compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Bilgewater Springs at #15,405, within the top 69% of ranked servers.

A.8What is the population level of Bilgewater Springs?

The current population of Bilgewater Springs is 0, drawn from 50 slots. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.9What do the tags associated with Bilgewater Springs signify?

gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): It offers 50 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166494 (Build): This server runs game build 166494; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags Bilgewater Springs publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can Bilgewater Springs be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Bilgewater Springs: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11What are the settings and rules that govern Bilgewater Springs?

Its name carries no gather rate for Bilgewater Springs. The group cap is 8 players, which is the default in the game. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on Bilgewater Springs?

Generated by the game from seed 966022937, the procedural map on Bilgewater Springs measures 4,500. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining Bilgewater Springs?

Enter client.connect 172.240.229.155:28055 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp50Max players. It offers 50 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. Your game must run protocol 2634 to connect.
cs166494Build. This server runs game build 166494.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.