A quiet classroom so far: 0 of 8 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,388 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 158 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
W······
W······
W······
W······
W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Monday 2 November, 04:09 UTC, in 5d 7h.
Every Monday at 04:09 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak0players, last three wipes
Coming wipes
5d 7hMon 2 Nov, 04:09 UTC
8d 22hThu 5 Nov, 19:00 UTCFW
12d 7hMon 9 Nov, 04:09 UTC
19d 7hMon 16 Nov, 04:09 UTC
26d 7hMon 23 Nov, 04:09 UTC
33d 7hMon 30 Nov, 04:09 UTC
36d 22hThu 3 Dec, 19:00 UTCFW
40d 7hMon 7 Dec, 04:09 UTC
The first 48 hours of its last wipes
Mon 19 OctMon 12 OctMon 5 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 04:09 UTC1d ago
–
–
running
0
Mon 19 Oct, 04:08 UTC8d ago
0
–
7 days
0
Mon 12 Oct, 04:13 UTC15d ago
0
–
7 days
0
Mon 5 Oct, 04:08 UTC22d ago
0
–
7 days
0
Mon 28 Sep, 04:10 UTC29d ago
0
–
7 days
0
Mon 21 Sep, 04:05 UTC36d ago
0
–
7 days
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Rust lifecycle test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 141.94.64.178:48015.
How dependable is Rust lifecycle test, and is it online at the moment?
You cannot join now: Rust lifecycle test is offline, last seen 39 hours ago. For the last 7 full days, it was up 1 of 168 hours, or 1% of the time. The first sighting by Rust Server Score was on 14 September 2026.
What Rust version is Rust lifecycle test on?
The server Rust lifecycle test is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Rust lifecycle test wipe, and how often?
The wipe rhythm on Rust lifecycle test is every Monday at 04:09 UTC. Expect the next wipe on Monday 2 November at 04:09 UTC. The world it runs now was created 40 hours.
What happens on Rust lifecycle test when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
What position does Rust lifecycle test hold in the rankings?
In the top 70% of all ranked servers, Rust lifecycle test sits at #15,388 for player hours over the last seven days.
What does the population on Rust lifecycle test look like?
It has been 39 hours since Rust lifecycle test was last seen, and it is offline right now. Over the past seven days, the average player count was 0.
Lists and filters
What do Rust lifecycle test's tags stand for?
You'll see Rust lifecycle test tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp8 (Max players): Its slot count is 8; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Rust lifecycle test?
These Rust Server Score lists count Rust lifecycle test among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
What settings and rules apply on Rust lifecycle test?
Nothing in the name of Rust lifecycle test states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Rust lifecycle test runs which map?
Rust lifecycle test runs a procedural map, which the game generates.
Getting in
What is the way to join Rust lifecycle test?
Enter client.connect 141.94.64.178:48015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp8
Max playersIts slot count is 8.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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.
A term to build on. Strongest in momentum (D); population is the one to work on (F).