A quiet classroom so far: 0 of 10 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,954 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 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
38/ 100
F
Slipped a little: down 3,546 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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
Every five minutes, from the Steam server list.
AveragePeak
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 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 22:03 UTC5d 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. 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 Testing. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 90.146.82.82:28035.
Is Testing up, and how steady is its uptime?
You can join now: Testing is online. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 6 October 2026.
What Rust version is Testing on?
You will find Testing on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Testing wipe its map?
Testing has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 5 days 23 hours.
What should you expect from wipe day on Testing?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 4 hours after it began.
Player numbers
Where does Testing sit among Rust servers?
In the top 67% of all ranked servers, Testing sits at #14,954 for player hours over the last seven days.
What does the population on Testing look like?
Right now, 0 players are on Testing, which has 10 slots. The seven-day average is 0 players, with a peak of 1.
Lists and filters
How should you read the tags on Testing?
gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): Its slot count is 10; 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): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Testing 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.
Which lists and filters on Rust Server Score show Testing?
These Rust Server Score lists count Testing among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is Testing set up, and what rules does it keep?
You will find no gather rate in the name of Testing. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Testing runs which map?
A procedural map, generated by the game, is what Testing runs.
Connecting
What is the way to join Testing?
To connect, start Rust, press F1, and type client.connect 90.146.82.82:28035. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
Game modeThis is vanilla survival.
mp10
Max playersIts slot count is 10.
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
ModdedThe game is changed by plugins or settings; you will find it 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 uptime (A); population is the one to work on (F).