Working its way up from the back of the class: #15,627 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
33/ 100
F
Lost ground: down 5,374 places this week. A strong wipe could turn it round.
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 71% 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
Which region is xJermelz's v0.8.7 Train Test based in?
No region is published for xJermelz's v0.8.7 Train Test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 66.9.164.119:28415.
How reliable is xJermelz's v0.8.7 Train Test, and is it up?
The server is down: xJermelz's v0.8.7 Train Test is offline now, with the last sighting 17 days 17 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 11 October 2026, Rust Server Score saw it for the first time.
Which Rust version is xJermelz's v0.8.7 Train Test running?
You will find xJermelz's v0.8.7 Train Test on Rust network protocol 2634 and build 167398, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does xJermelz's v0.8.7 Train Test reset?
The record holds too few of xJermelz's v0.8.7 Train Test's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 27 days 17 hours have passed since this world was made.
Player count
What position does xJermelz's v0.8.7 Train Test hold in the rankings?
Over the last seven days, xJermelz's v0.8.7 Train Test has #15,627 for player hours, in the top 71% of all ranked servers.
How many players does xJermelz's v0.8.7 Train Test usually have?
xJermelz's v0.8.7 Train Test is offline at the moment; the last time it was seen was 17 days 17 hours ago.
Tags
How should you read the tags on xJermelz's v0.8.7 Train Test?
gmvanilla (Game mode): Survival, vanilla style; mp5 (Max players): Its slot count is 5; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags xJermelz's v0.8.7 Train Test publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature xJermelz's v0.8.7 Train Test?
These Rust Server Score lists count xJermelz's v0.8.7 Train Test among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on xJermelz's v0.8.7 Train Test?
The name of xJermelz's v0.8.7 Train Test gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map xJermelz's v0.8.7 Train Test uses?
The game generates a procedural map for xJermelz's v0.8.7 Train Test.
Getting in
How should you connect to xJermelz's v0.8.7 Train Test?
Enter client.connect 66.9.164.119:28415 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 asmp5,ptrak,$r?,v2634,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp5
Max playersIts slot count is 5.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is 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.