On the class lists: F (30), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average0peak –
Rank#15,388top 70%
Last wipe10d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,388 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); population 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 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
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
TEST SERVER leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 91.83.37.21:28015.
How reliable is TEST SERVER, and is it up?
At this moment, TEST SERVER is offline; the last time it was seen was 2 days 1 hours ago. It was up 0 of 24 hours over the last 1 full day, which is 0% of the time. It was first seen by Rust Server Score on 25 October 2026.
What Rust version is TEST SERVER on?
The server TEST SERVER is on Rust network protocol 2635 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does TEST SERVER wipe, and how often?
There are too few wipes on record for TEST SERVER to show a 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 10 days 8 hours.
Population
What position does TEST SERVER hold in the rankings?
Over the last seven days, TEST SERVER has #15,388 for player hours, in the top 70% of all ranked servers.
How many players does TEST SERVER usually have?
The last sighting of TEST SERVER was 2 days 1 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Tags and filters
How should you read the tags on TEST SERVER?
gmvanilla (Game mode): This is vanilla survival; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs167781 (Build): Build number: 167781; 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): Plugins or settings alter the game, so it sits under Modded are the tags TEST SERVER publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does TEST SERVER appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TEST SERVER among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
What settings and rules apply on TEST SERVER?
You will find no gather rate in the name of TEST SERVER. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: 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 not covered by VAC, Valve's anti-cheat.
Can you tell me which map TEST SERVER uses?
A procedural map, generated by the game, is what TEST SERVER runs.
How to join
What is the way to join TEST SERVER?
To connect, start Rust, press F1, and type client.connect 91.83.37.21:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs167781
BuildBuild number: 167781.
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
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. Strongest in standing (F); population is the one to work on (F).