Working its way up from the back of the class: #11,487 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
36/ 100
F
Slipped a little: down 3,218 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in standing (D); momentum 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.
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 53% 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 15h.
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
No region is published for Test Server - Dont enter. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 181.21.28.67:28015.
How dependable is Test Server - Dont enter, and is it online at the moment?
You cannot join now: Test Server - Dont enter is offline, last seen 11 days 23 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 16 October 2026.
On what Rust version does Test Server - Dont enter sit?
Rust network protocol 2634 and build 167781 on Windows is what Test Server - Dont enter runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Test Server - Dont enter reset?
the force wipe gives the basis for estimating Test Server - Dont enter's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 12 days 4 hours have passed since this world was made. The tags show a monthly wipe schedule.
Population
Where does Test Server - Dont enter sit among Rust servers?
In the top 53% of all ranked servers, Test Server - Dont enter sits at #11,487 for player hours over the last seven days.
Is Test Server - Dont enter a busy server?
It has been 11 days 23 hours since Test Server - Dont enter was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on Test Server - Dont enter?
You'll see Test Server - Dont enter tagged with gmvanilla (Game mode): This is vanilla survival; mp3 (Max players): Its slot count is 3; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. 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.
Which lists and filters on Rust Server Score show Test Server - Dont enter?
These Rust Server Score lists count Test Server - Dont enter among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
Server rules
How is Test Server - Dont enter set up, and what rules does it keep?
Nothing in the name of Test Server - Dont enter states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Test Server - Dont enter?
A procedural map, generated by the game, is what Test Server - Dont enter runs.
How to join
What is the way to join Test Server - Dont enter?
Enter client.connect 181.21.28.67:28015 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 asmp3,ptrak,$r?,v2634,^z,^y,^m,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp3
Max playersIts slot count is 3.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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 (D); momentum is the one to work on (F).