Working its way up from the back of the class: #14,465 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
38/ 100
F
Slipped a little: down 3,369 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 61% 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
In what location does xJermelz's v0.8.3 SafePoint Test sit?
xJermelz's v0.8.3 SafePoint Test leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 66.9.164.218:28315 is the address to use.
How reliable is xJermelz's v0.8.3 SafePoint Test, and is it up?
You cannot join now: xJermelz's v0.8.3 SafePoint Test is offline, last seen 30 days 3 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 28 September 2026.
What Rust version is xJermelz's v0.8.3 SafePoint Test on?
The server xJermelz's v0.8.3 SafePoint Test is on Rust network protocol 2633 and build 165217 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does xJermelz's v0.8.3 SafePoint Test wipe its map?
There are too few wipes on record for xJermelz's v0.8.3 SafePoint Test to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 32 days 7 hours have passed since this world was made.
Player numbers
Where does xJermelz's v0.8.3 SafePoint Test place in the wider field of Rust servers?
In the top 61% of all ranked servers, xJermelz's v0.8.3 SafePoint Test sits at #14,465 for player hours over the last seven days.
Is xJermelz's v0.8.3 SafePoint Test a busy server?
It has been 30 days 3 hours since xJermelz's v0.8.3 SafePoint Test was last seen, and it is offline right now.
Tags
What is meant by the tags on xJermelz's v0.8.3 SafePoint Test?
You'll see xJermelz's v0.8.3 SafePoint Test tagged with gmvanilla (Game mode): This is vanilla survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: 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. 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.
Where does xJermelz's v0.8.3 SafePoint Test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include xJermelz's v0.8.3 SafePoint Test: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does xJermelz's v0.8.3 SafePoint Test enforce, and what are its settings?
The name of xJermelz's v0.8.3 SafePoint Test gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, 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. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
xJermelz's v0.8.3 SafePoint Test runs which map?
The game generates a procedural map for xJermelz's v0.8.3 SafePoint Test.
How to join
How should you connect to xJermelz's v0.8.3 SafePoint Test?
To connect, start Rust, press F1, and type client.connect 66.9.164.218:28315. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmvanilla,cs165217,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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. Even marks across the subjects, from F to F.