Working its way up from the back of the class: #15,490 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 360 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.
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
No region is published for ExitTest. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 88.218.224.23:28020 is the address to use.
How reliable is ExitTest, and is it up?
At this moment, ExitTest is offline; the last time it was seen was 38 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does ExitTest sit?
Rust network protocol 2633 and build 163794 on Linux is what ExitTest runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does ExitTest wipe, and how often?
The record holds too few of ExitTest's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 38 days 19 hours.
Player count
Where does ExitTest place in the wider field of Rust servers?
In the top 70% of all ranked servers, ExitTest sits at #15,490 for player hours over the last seven days.
Is ExitTest a busy server?
ExitTest is offline at the moment; the last time it was seen was 38 days 19 hours ago.
Lists and filters
What is meant by the tags on ExitTest?
The game's browser takes its cue from the tags ExitTest has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. 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 ExitTest?
Rust Server Score lists that include ExitTest: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
What settings and rules apply on ExitTest?
You will find no gather rate in the name of ExitTest. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
ExitTest runs which map?
A procedural map, generated by the game, is what ExitTest runs.
Getting in
How do you get onto ExitTest?
Enter client.connect 88.218.224.23:28020 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 asmp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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).