On the class lists: F (28), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average0peak 1
Rank#11,300top 51%
Last wipe3d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
33/ 100
F
A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
49/ 100
D
Working its way up from the back of the class: #11,300 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
35/ 100
F
Slipped a little: down 3,424 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in standing (D); wipes are 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 51% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
····WW·
·······
·····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.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4
The first 48 hours of its last wipes
Sat 24 OctSat 10 OctSat 10 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 10:11 UTC3d ago
1
–
running
1
Sat 10 Oct, 11:01 UTC17d ago
0
–
14 days
0
Sat 10 Oct, 02:12 UTC17d ago
1
–
0.4 days
1
Fri 9 Oct, 08:40 UTC18d ago
1
–
0.7 days
0
Thu 1 Oct, 11:21 UTC26d ago
1
halved by day 4
7.9 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
Vanilla Testing Lab 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 76.27.9.185:28015.
Is Vanilla Testing Lab up, and how steady is its uptime?
The server is down: Vanilla Testing Lab is offline now, with the last sighting 3 days 3 hours ago. It was up 7% of the time over the last 7 full days, 12 of 168 hours. On 18 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Vanilla Testing Lab running?
The server Vanilla Testing Lab is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Vanilla Testing Lab wipe, and how often?
Vanilla Testing Lab wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 3 days 9 hours have passed since this world was made.
What should you expect from wipe day on Vanilla Testing Lab?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Player count
Where does Vanilla Testing Lab place in the wider field of Rust servers?
In the top 51% of all ranked servers, Vanilla Testing Lab sits at #11,300 for player hours over the last seven days.
What does the population on Vanilla Testing Lab look like?
It has been 3 days 3 hours since Vanilla Testing Lab was last seen, and it is offline right now. The seven-day average is 0 players, with a peak of 1.
Tags and filters
How should you read the tags on Vanilla Testing Lab?
The game's browser takes its cue from the tags Vanilla Testing Lab has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Its slot count is 1; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. 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 Vanilla Testing Lab appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Vanilla Testing Lab among them: 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 week.
Rules and settings
Which rules does Vanilla Testing Lab enforce, and what are its settings?
Nothing in the name of Vanilla Testing Lab states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Vanilla Testing Lab runs which map?
Vanilla Testing Lab runs a procedural map, which the game generates.
How to join
How should you connect to Vanilla Testing Lab?
To connect, start Rust, press F1, and type client.connect 76.27.9.185:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersIts slot count is 1.
ts8
Group limitA team can hold 8 at most, which is the game default.
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 codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework 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 standing (D); wipes are the one to work on (F).