Working its way up from the back of the class: #15,478 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
51/ 100
D
Moving up: up 372 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.
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.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 18 Sep. 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. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The 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 TEST SERVER. Rust Server Score takes the server's word for its location and does not trace the hardware. 61.105.188.200:28015 is the address to use.
How reliable is TEST SERVER, and is it up?
The server is down: TEST SERVER is offline now, with the last sighting 40 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is TEST SERVER running?
The server TEST SERVER is on Rust network protocol 2633 and build 163794 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does TEST SERVER wipe, and how often?
The estimate for TEST SERVER's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 45 days 23 hours. Its tags say it wipes every two weeks.
Population
Where does TEST SERVER sit among Rust servers?
Over the last seven days, TEST SERVER has #15,478 for player hours, in the top 70% of all ranked servers.
How many players does TEST SERVER usually have?
TEST SERVER is offline at the moment; the last time it was seen was 40 days 20 hours ago.
Tags and filters
What do TEST SERVER's tags stand for?
You'll see TEST SERVER tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^r (Roleplay): You play a role on this server; ^p (PvE): This is player against world: players do not fight each other; ^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 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 TEST SERVER?
These Rust Server Score lists count TEST SERVER among them: Modded Rust servers, graded, Rust PvE servers, graded and Roleplay servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Roleplay ^r, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Server rules
What settings and rules apply on TEST SERVER?
The name of TEST SERVER gives no gather rate. The default of 8 players applies as the group cap. roleplay is the mode here, roleplay rules, towns and jobs. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
TEST SERVER runs which map?
The game generates the procedural map on TEST SERVER at size 2,000 with seed 4. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to TEST SERVER?
To connect, start Rust, press F1, and type client.connect 61.105.188.200:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,^b,^r,^p,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Gameplay
^r
RoleplayYou play a role on this server.
^p
PvEThis is player against world: players do not fight each other.
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. Strongest in momentum (D); standing is the one to work on (F).