Not ranked yet, so there is no place in the school to report.
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
20/ 100
F
Lost ground: down 9,347 places this week. A strong wipe could turn it round.
A term to build on.
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.
AveragePeak
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
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 5h.
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
TEST SERVER leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 1.171.21.17:28215 is the address to use.
Is TEST SERVER up, and how steady is its uptime?
At this moment, TEST SERVER is offline; the last time it was seen was 38 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 18 September 2026.
What Rust version is TEST SERVER on?
Rust network protocol 2633 and build 164530 on Windows is what TEST SERVER runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does TEST SERVER wipe its map?
The next wipe on TEST SERVER is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 53 days 4 hours. Its tags list a monthly wipe schedule.
Player count
What position does TEST SERVER hold in the rankings?
Over the last seven days, TEST SERVER has #15,502 for player hours, in the top – of all ranked servers.
What does the population on TEST SERVER look like?
TEST SERVER is offline at the moment; the last time it was seen was 38 days 20 hours ago.
Lists and filters
What is meant by the tags on TEST SERVER?
The game's browser takes its cue from the tags TEST SERVER has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^s (Softcore): On death you keep part of your inventory: that is Facepunch's easier mode; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature TEST SERVER?
These Rust Server Score lists count TEST SERVER among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE and Softcore; Server tag: Monthly ^m, Softcore ^s, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
How is TEST SERVER set up, and what rules does it keep?
Nothing in the name of TEST SERVER states a gather rate. The default of 8 players applies as the group cap. It runs softcore, Facepunch's easier setting, with part of your loot kept. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map TEST SERVER uses?
A procedural map, generated by the game, is what TEST SERVER runs.
Connecting
What is the way to join TEST SERVER?
Enter client.connect 1.171.21.17:28215 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 asmp20,ptrak,$r?,v2633,^m,^s,^p,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^s
SoftcoreOn death you keep part of your inventory: that is Facepunch's easier mode.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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.