On the class lists: F (44), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#11,874top 53%
Last wipe14d agomonthly schedule
Next wipe7d 19hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
95/ 100
A+
A full classroom nearly all week: 1 of 1 on average.
Standingrank on player hours
47/ 100
D
Working its way up from the back of the class: #11,874 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 73 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
30/ 100
F
Lost ground: down 4,737 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in performance (A+); uptime 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 14 Oct. 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 19h.
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
You'll find no region listed by Dark_Ghost Test. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 2.82.186.229:28015.
How reliable is Dark_Ghost Test, and is it up?
You cannot join now: Dark_Ghost Test is offline, last seen 44 hours ago. About 1 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 2 of 168 hours, or 1% of the time. It was first seen by Rust Server Score on 14 October 2026.
Does Dark_Ghost Test perform well?
It never fell below 53 server fps in the last 48 hours, averaging 73. Up to 69,057 entities were in the world, covering buildings, deployables and the rest. Up to 1,720 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does Dark_Ghost Test sit?
Rust network protocol 2635 and build 168909 on Windows is what Dark_Ghost Test runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Dark_Ghost Test wipe, and how often?
the force wipe gives the basis for estimating Dark_Ghost Test's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 14 days 1 hours have passed since this world was made. Its tags record that it wipes monthly.
Player count
Where does Dark_Ghost Test place in the wider field of Rust servers?
Over the last seven days, Dark_Ghost Test has #11,874 for player hours, in the top 53% of all ranked servers.
Is Dark_Ghost Test a busy server?
Dark_Ghost Test is offline at the moment; the last time it was seen was 44 hours ago. Averaging 1 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 02:00 UTC, averaging 1 players.
Tags
How should you read the tags on Dark_Ghost Test?
The game's browser takes its cue from the tags Dark_Ghost Test has set: gmvanilla (Game mode): You play vanilla survival here; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. 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 Dark_Ghost Test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Dark_Ghost Test: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does Dark_Ghost Test enforce, and what are its settings?
You will find no gather rate in the name of Dark_Ghost Test. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on Dark_Ghost Test?
A procedural map of size 3,500 and seed 295700, generated by the game, is what Dark_Ghost Test runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to Dark_Ghost Test?
To connect, start Rust, press F1, and type client.connect 2.82.186.229: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,^m,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 fair term, with more to come. Strongest in performance (A+); uptime is the one to work on (F).