Working its way up from the back of the class: #15,982 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
24/ 100
F
Lost ground: down 8,247 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.
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
No region is published for TestServer. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 91.67.226.203:28015 is the address to use.
How reliable is TestServer, and is it up?
The server is down: TestServer is offline now, with the last sighting 22 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 4 October 2026, Rust Server Score saw it for the first time.
Which Rust version is TestServer running?
The server TestServer is on Rust network protocol 2634 and build 166652 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does TestServer reset?
TestServer 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. The world it runs now was created 23 days 16 hours.
Player numbers
What position does TestServer hold in the rankings?
Over the last seven days, TestServer has #15,982 for player hours, in the top 71% of all ranked servers.
What does the population on TestServer look like?
TestServer is offline at the moment; the last time it was seen was 22 days 20 hours ago.
Tags and filters
What is meant by the tags on TestServer?
The game's browser takes its cue from the tags TestServer has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. 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 TestServer?
Rust Server Score lists that include TestServer: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is TestServer set up, and what rules does it keep?
Nothing in the name of TestServer states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map TestServer uses?
A procedural map of size 4,000 and seed 12345, generated by the game, is what TestServer runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto TestServer?
Enter client.connect 91.67.226.203: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 asmp10,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from F to F.