On the class lists: F (30), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak –
Rank#15,373top 69% · #1531 in NA
Last wipe4d agoweekly schedule
Next wipe2d 20hSat 31 Oct, 16:01 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,373 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 239 server fps on average.
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
25/ 100
F
Lost ground: down 7,618 places this week. A strong wipe could turn it round.
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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 16 Oct. 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 82% in NA, and #370 of the duo servers (top 88%). Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·····W·
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Saturday 31 October, 16:01 UTC, in 2d 20h.
Its weekly schedule tag · low confidence
usual gap4.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
2d 20hSat 31 Oct, 16:01 UTC
7d 23hThu 5 Nov, 19:00 UTCFW
9d 20hSat 7 Nov, 16:01 UTC
16d 20hSat 14 Nov, 16:01 UTC
23d 20hSat 21 Nov, 16:01 UTC
30d 20hSat 28 Nov, 16:01 UTC
35d 23hThu 3 Dec, 19:00 UTCFW
37d 20hSat 5 Dec, 16:01 UTC
The first 48 hours of its last wipes
Sat 24 OctSat 17 OctFri 16 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
Sat 24 Oct, 16:01 UTC4d ago
0
–
running
0
Sat 17 Oct, 15:10 UTC11d ago
1
halved by day 1
7 days
1
Fri 16 Oct, 10:42 UTC12d ago
1
–
1.2 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
In North America, according to its own listing, sits testing, with the NA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 157.85.86.76:21595.
Is testing up, and how steady is its uptime?
You can join now: testing is online. According to its reported uptime, the last restart was about 2 days 5 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
How well does testing run?
It never fell below 231 server fps in the last 48 hours, averaging 239. Buildings, deployables and everything else in the world added up to as many as 7,087 entities. Up to 2,814 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is testing running?
The server testing is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does testing wipe its map?
Too few wipes on testing are recorded to confirm the schedule, so its tag guides the prediction. Expect the next wipe on Saturday 31 October at 16:01 UTC. The world it runs now was created 4 days 3 hours. Wipes are scheduled weekly, according to its tags.
What happens on testing when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Population
Where does testing sit among Rust servers?
Over the last seven days, testing has #15,373 for player hours, in the top 69% of all ranked servers and #1,531 in North America. It comes #370 among servers in the duo group.
Is testing a busy server?
Right now, 0 players are on testing, which has 20 slots. For the last seven days, the average number of players was 0.
Tags and filters
What is meant by the tags on testing?
You'll see testing tagged with gmvanilla (Game mode): You play vanilla survival here; mp20 (Max players): 20 slots are available; ts2 (Group limit): A team can hold 2 players at most; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): You will find it under North America in the browser 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 testing?
These Rust Server Score lists count testing among them: Duo servers, marked like a report, Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly; 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. 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. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on testing?
testing runs a game-generated procedural map at size 1,000, seed 50000. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Connecting
How should you connect to testing?
Enter client.connect 157.85.86.76:21595 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/BGKzykfwEC.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,^z,^y,^w,NA,gmvanilla,cs168909,ts2
Game
gmvanilla
Game modeYou play vanilla survival here.
mp20
Max players20 slots are available.
ts2
Group limitA team can hold 2 players at most.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
Region
NA
North AmericaYou will find it under North America in the browser.
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).