On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,326top 69% · #1505 in NA
Last wipe14d agobiweekly schedule
Next wipe7d 5hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 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,326 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
49/ 100
D
Slipped a little: down 201 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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.
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.
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 17 Sep. 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 81% in NA. 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
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h.
The force wipe · high confidence
usual gap14.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
Coming wipes
7d 5hThu 5 Nov, 19:00 UTCFW
13d 4hWed 11 Nov, 18:29 UTC
27d 4hWed 25 Nov, 18:29 UTC
35d 5hThu 3 Dec, 19:00 UTCFW
41d 4hWed 9 Dec, 18:29 UTC
The first 48 hours of its last wipes
Wed 14 OctSat 3 OctTue 15 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 18:29 UTC14d ago
3
–
running
0
Sat 3 Oct, 13:58 UTC25d ago
–
–
11.2 days
0
Tue 15 Sep, 14:33 UTC43d ago
0
–
18 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
The NA tag on Testing Testing puts it in North America. Rust Server Score takes the server's word for its location and does not trace the hardware. 66.51.99.65:28010 is the address to use.
How dependable is Testing Testing, and is it online at the moment?
The server is down: Testing Testing is offline now, with the last sighting 5 days 16 hours ago. It was up 27% of the time over the last 7 full days, 46 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
What Rust version is Testing Testing on?
Rust network protocol 2634 and build 167781 on Linux is what Testing Testing runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Testing Testing wipe its map?
Its tag sets the prediction, as the record holds too few of Testing Testing's wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 14 days 19 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on Testing Testing?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
What position does Testing Testing hold in the rankings?
Over the last seven days, Testing Testing has #15,326 for player hours, in the top 69% of all ranked servers and #1,505 in North America.
What does the population on Testing Testing look like?
Testing Testing is offline at the moment; the last time it was seen was 5 days 16 hours ago. For the last seven days, the average number of players was 0.
Tags
What do Testing Testing's tags stand for?
You'll see Testing Testing tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): The danger comes from the world, not from other players; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here; NA (North America): You will find it under North America in the browser 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.
Which lists and filters on Rust Server Score show Testing Testing?
Rust Server Score lists that include Testing Testing: Modded Rust servers, graded, Rust PvE servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
Which rules does Testing Testing enforce, and what are its settings?
The name of Testing Testing gives no gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Testing Testing?
Testing Testing runs a game-generated procedural map at size 5,000, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
How to join
How should you connect to Testing Testing?
To connect, start Rust, press F1, and type client.connect 66.51.99.65:28010. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^z,^y,^b,NA,^p,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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.
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 momentum (D); population is the one to work on (F).