Working its way up from the back of the class: #13,590 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
31/ 100
F
Lost ground: down 5,056 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 62% of all ranked servers, and #584 of the quad servers (top 71%). 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
TestServer leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 221.227.64.112:10241 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 18 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 11 October 2026.
What Rust version is TestServer on?
Rust network protocol 2634 and build 167231 on Windows is what TestServer runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does TestServer wipe its map?
There are too few wipes on record for TestServer to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 27 days 19 hours have passed since this world was made.
Player numbers
What position does TestServer hold in the rankings?
Over the last seven days, TestServer has #13,590 for player hours, in the top 62% of all ranked servers. It comes #584 among servers in the quad group.
Is TestServer a busy server?
TestServer is offline at the moment; the last time it was seen was 18 days 9 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; mp100 (Max players): Its slot count is 100; ts4 (Group limit): A team can hold 4 players at most; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under 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?
Rust Server Score lists that include TestServer: Modded Rust servers, graded. You can find it under these server-list filters: 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). You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Getting in
How should you connect to TestServer?
To connect, start Rust, press F1, and type client.connect 221.227.64.112: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 modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts4
Group limitA team can hold 4 players at most.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.