Rust StatisticsWorking papers on every public Rust server · 34,406 players now

Rust lifecycle test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 2d ago · 141.94.64.178:48015

Abstract

We describe the public Rust server Rust lifecycle test, reached at 141.94.64.178:48015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,419 of all servers, the top 69%. It last wiped 2d ago; the next wipe is expected Monday 2 November, 04:09 UTC, every Monday at 04:09 UTC.

Keywordsrust server

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/80% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,419top 69%
Last wipe2d agono schedule published
Next wipe34d 22hMon 2 Nov, 04:09 UTC

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.

No hourly history yet.
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
This server has not answered a direct query in the last 48 hours.
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.

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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: fixed weekdays

The next wipe is expected Monday 2 November, 04:09 UTC, in 4d 22h. Every Monday at 04:09 UTC (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap7 daysbetween real wipes
On rhythm100%of its recent wipes
Wipe-day peak0players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Mon 2 Nov, 04:094d 22hits own schedule
Thu 5 Nov, 19:008d 13hforce wipefw
Mon 9 Nov, 04:0911d 22hits own schedule
Mon 16 Nov, 04:0918d 22hits own schedule
Mon 23 Nov, 04:0925d 22hits own schedule
Mon 30 Nov, 04:0932d 22hits own schedule
Thu 3 Dec, 19:0036d 13hforce wipefw
Mon 7 Dec, 04:0939d 22hits own schedule
Mon 26 OctMon 19 OctMon 12 Oct
01234+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 0, 0 hours in.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 04:092d ago 0 – running 0
Mon 19 Oct, 04:089d ago 0 – 7 d 0
Mon 12 Oct, 04:1316d ago 0 – 7 d 0
Mon 5 Oct, 04:0823d ago 0 – 7 d 0
Mon 28 Sep, 04:1030d ago 0 – 7 d 0
Mon 21 Sep, 04:0537d ago 0 – 7 d 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

No map picture published
Figure 5: The map: Procedural Map.
Table 5: The server's published settings.
Address141.94.64.178:48015
Region–
Max players8
Group limit8, the default
Wipe schedule–
Last wipe26 Oct 2026, 04:09 UTC
Hostname–
First seen14 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust community servers listed [2] and Rust wipe forecast [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 534 on average248/275
Rustoria.co - EU MainEU · groups of 16+ · weekly · 322 on average21/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 321 on average16/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average170/200
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average64/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average37/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does Rust lifecycle test have?

There is no region published for Rust lifecycle test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 141.94.64.178:48015.

A.2What is the reliability of Rust lifecycle test, and is it online?

Rust lifecycle test is currently offline, with the last sighting 2 days 1 hours ago. The server was up 1% of the time over the last 7 full days, 1 of 168 hours. It was first observed on 14 September 2026 by Rust Statistics.

A.3What version of Rust is run on Rust lifecycle test?

The version of Rust on Rust lifecycle test is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4On what cycle does Rust lifecycle test wipe?

Wipes at Rust lifecycle test occur every Monday at 04:09 UTC. The server is due to wipe on Monday 2 November at 04:09 UTC. The current world has been running for 2 days 1 hours.

A.5What happens on Rust lifecycle test when wipe day arrives?

Across its recent wipes, the average peak population was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6What is the rank of Rust lifecycle test among Rust servers?

The seven-day player-hours ranking puts Rust lifecycle test at #15,419, within the top 69% of ranked servers.

A.7At what level does Rust lifecycle test operate in terms of players?

At this moment Rust lifecycle test is offline, having last been seen 2 days 1 hours ago. The mean population for the last seven days is 0.

Tags and filters

A.8How should the tags on Rust lifecycle test be interpreted?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp8 (Max players): 8 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset, which Rust lifecycle test publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Rust lifecycle test be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that Rust lifecycle test fits. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Settings and map

A.10Which settings and rules are in force on Rust lifecycle test?

No gather rate appears in the name of Rust lifecycle test. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

A.11What is the map for Rust lifecycle test?

A procedural map, generated by the game, is what Rust lifecycle test runs.

Connection

A.12What is the process for joining Rust lifecycle test?

Press F1 inside Rust to open the console and enter client.connect 141.94.64.178:48015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp8,ptrak,$r?,v2635,gmrust,cs168909,ts8.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp8Max players. 8 slots are available.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. This server runs game build 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.

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. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.