Working its way up from the back of the class: #15,256 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
25/ 100
F
Lost ground: down 7,610 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
No daily history yet.
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 69% of all ranked servers, top 84% in NA, and #378 of the duo servers (top 89%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Saturday 31 October, 15:49 UTC, in 2d 8h.
Weekly: 7 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
You'll see testing listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 153.66.141.222:28015 is the address to use.
Is testing up, and how steady is its uptime?
You cannot join now: testing is offline, last seen 10 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 18 October 2026.
Which Rust version is testing running?
Rust network protocol 2634 and build 166652 on Windows is what testing runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does testing reset?
The next wipe on testing is a projection from weekly: 7 days after its last wipe. Expect the next wipe on Saturday 31 October at 15:49 UTC. It has been running its current world for 18 days 15 hours. The tags carry a weekly wipe schedule.
Player count
Where does testing sit among Rust servers?
In North America, testing is #1,560, and overall it is #15,256 on player hours over the last seven days, in the top 69% of all ranked servers. In the duo group, it ranks #378.
How many players does testing usually have?
testing is offline at the moment; the last time it was seen was 10 days 11 hours ago.
Tags
What do testing's tags stand for?
You'll see testing tagged with gmvanilla (Game mode): Survival, vanilla style; mp20 (Max players): Its slot count is 20; ts2 (Group limit): No team may go above 2; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here; NA (North America): The server browser lists it under North America in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does testing appear in the Rust Server Score lists and filters?
Rust Server Score lists that include testing: Duo servers, marked like a report, Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly.
Server rules
What settings and rules apply on testing?
The name of testing gives no gather rate. You can have up to 2 players in a group (duo). survival is the mode here, 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.
Connecting
How do you get onto testing?
Enter client.connect 153.66.141.222:28015 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 asmp20,ptrak,$r?,v2634,^z,^y,^w,NA,gmvanilla,cs166652,ts2
Game
gmvanilla
Game modeSurvival, vanilla style.
mp20
Max playersIts slot count is 20.
ts2
Group limitNo team may go above 2.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework here.
Region
NA
North AmericaThe server browser lists it under North America.
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. Even marks across the subjects, from F to F.