On the class lists: F (36), with population over 48 hours and no performance mark.
Players now0/ 30% full
7-day average0peak 1
Rank#14,886top 67%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 3 on average. Plenty of space to grow.
Standingrank on player hours
33/ 100
F
Working its way up from the back of the class: #14,886 on player hours.
Uptimehours on the list, last 48
69/ 100
C+
Missed a few lessons: on the list 33 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 236 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 2,728 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); 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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·····W·
W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap4.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sat 24 OctSat 17 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, 20:37 UTC1d ago
–
–
running
0
Sat 24 Oct, 21:38 UTC3d ago
0
–
2 days
0
Sat 17 Oct, 18:27 UTC10d ago
1
–
7.1 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
PopulaceLab (test) leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 24.8.85.119:28335.
How reliable is PopulaceLab (test), and is it up?
You cannot join now: PopulaceLab (test) is offline, last seen 3 hours ago. According to its reported uptime, the last restart was about 31 hours ago. It was up 30 of 168 hours over the last 7 full days, which is 18% of the time. The first sighting by Rust Server Score was on 17 October 2026.
How well does PopulaceLab (test) run?
The average over the last 48 hours was 236 server fps, and it never went below 167. Up to 130,693 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 6,988 MB. When fps is low and entities climb, that is lag to players.
What Rust version is PopulaceLab (test) on?
You will find PopulaceLab (test) on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does PopulaceLab (test) wipe, and how often?
PopulaceLab (test) wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 35 hours have passed since this world was made.
What happens on PopulaceLab (test) when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does PopulaceLab (test) place in the wider field of Rust servers?
Over the last seven days, PopulaceLab (test) has #14,886 for player hours, in the top 67% of all ranked servers.
How many players does PopulaceLab (test) usually have?
PopulaceLab (test) is offline at the moment; the last time it was seen was 3 hours ago. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 22:00 UTC, averaging 0 players.
Tags and filters
What do PopulaceLab (test)'s tags stand for?
gmvanilla (Game mode): This is vanilla survival; mp3 (Max players): 3 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags PopulaceLab (test) publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does PopulaceLab (test) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include PopulaceLab (test): Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
How is PopulaceLab (test) set up, and what rules does it keep?
The name of PopulaceLab (test) gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map PopulaceLab (test) uses?
The game generates the procedural map on PopulaceLab (test) at size 4,500 with seed 1530458240. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Connecting
What is the way to join PopulaceLab (test)?
Enter client.connect 24.8.85.119:28335 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 asmp3,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
Game modeThis is vanilla survival.
mp3
Max players3 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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 performance (A+); population is the one to work on (F).