Working its way up from the back of the class: #15,271 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
30/ 100
F
Lost ground: down 5,959 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 70% of all ranked servers, and #629 of the quad servers (top 76%). 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
You'll find no region listed by TestServer. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 114.225.154.59:10241 is the address to use.
Is TestServer up, and how steady is its uptime?
The server is down: TestServer is offline now, with the last sighting 10 days 18 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 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 167231, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does TestServer reset?
The record holds too few of TestServer's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 27 days 4 hours.
Player count
What position does TestServer hold in the rankings?
In the top 70% of all ranked servers, TestServer sits at #15,271 for player hours over the last seven days. In the quad group, it ranks #629.
What does the population on TestServer look like?
It has been 10 days 18 hours since TestServer was last seen, and it is offline right now.
Lists and filters
What do TestServer's tags stand for?
The game's browser takes its cue from the tags TestServer has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts4 (Group limit): A team can hold 4 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does TestServer appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TestServer among them: 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: Quad.
Map and rules
What settings and rules apply on TestServer?
You will find no gather rate in the name of TestServer. You can have up to 4 players in a group (quad). It runs survival, 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. You are covered by VAC, Valve's anti-cheat.
Getting in
How do you get onto TestServer?
To connect, start Rust, press F1, and type client.connect 114.225.154.59:10241. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167231,ts4,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts4
Group limitA team can hold 4 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: 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. Even marks across the subjects, from F to F.