Working its way up from the back of the class: #12,911 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
53/ 100
D
Moving up: up 726 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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 60% 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. You can connect at 188.236.103.138:28015.
Is testserver up, and how steady is its uptime?
The server is down: testserver is offline now, with the last sighting 14 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 15 October 2026, Rust Server Score saw it for the first time.
On what Rust version does testserver sit?
You will find testserver on Rust network protocol 2634 and build 167058, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does testserver reset?
testserver has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 21 days 16 hours have passed since this world was made.
Population
What position does testserver hold in the rankings?
In the top 60% of all ranked servers, testserver sits at #12,911 for player hours over the last seven days.
What does the population on testserver look like?
The last sighting of testserver was 14 days 1 hours ago, and it is offline right now.
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): 10 slots are available; ts5 (Group limit): Teams cap out at 5; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167058 (Build): The game build is 167058; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is testserver set up, and what rules does it keep?
You will find no gather rate in the name of testserver. The limit for a group is 5 players. 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. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
testserver runs which map?
A procedural map, generated by the game, is what testserver runs.
Getting in
How do you get onto testserver?
To connect, start Rust, press F1, and type client.connect 188.236.103.138:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167058,ts5,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts5
Group limitTeams cap out at 5.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167058
BuildThe game build is 167058.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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); standing is the one to work on (F).