Rust Server TrendsSeismic network · station log
Recording Stations11,713 Players43,388 Active3,068 Wipes · 3 h103 48 h

Station XX-15326 · no signal

-=Dimikastafari=- Staging Test

Offline 80.200.23.239:28015 checked 9d ago

moddedcarbon
Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,326
top 69%
Last wipe
30d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15326 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 2 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep2 Oct7 Oct12 Oct21 Oct26 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
0.5 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
2players, last three wipes

The first 48 hours of its last wipes

Mon 28 SepMon 28 SepSun 27 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 4 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 28 Sep, 21:51 UTC30d ago M0.0rising 2 – running 1
Mon 28 Sep, 09:17 UTC30d ago M0.3rising 2 – 0.5 days 0
Sun 27 Sep, 21:20 UTC31d ago M0.3rising 2 – 0.5 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 155 on average
34/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
34/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average
31/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
6/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
4/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on -=Dimikastafari=- Staging Test?

The map on -=Dimikastafari=- Staging Test is procedural, produced by the game.

Which settings and rules apply on -=Dimikastafari=- Staging Test?

No gather rate appears in the name of -=Dimikastafari=- Staging Test. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on -=Dimikastafari=- Staging Test right now?

No players are recorded on -=Dimikastafari=- Staging Test at this moment; it is offline, and the last sighting was 9 days 3 hours ago.

How does -=Dimikastafari=- Staging Test rank against other Rust servers?

Over the last seven days, -=Dimikastafari=- Staging Test recorded enough player hours to reach #15,326 worldwide, placing it in the top 69% of all ranked servers.

Server facts

How reliably does -=Dimikastafari=- Staging Test stay online?

As recorded now, -=Dimikastafari=- Staging Test is not reachable, the last contact having been 9 days 3 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 27 September 2026.

Where in the world is -=Dimikastafari=- Staging Test hosted?

No region is published by -=Dimikastafari=- Staging Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 80.200.23.239:28015 is the address it uses.

What build of Rust does -=Dimikastafari=- Staging Test use?

-=Dimikastafari=- Staging Test is running Rust network protocol 2635 and build 168464 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on -=Dimikastafari=- Staging Test?

2 players, on average, was the busiest crowd at its recent wipes. 4 hours after the latest wipe, the crowd peaked.

How often does -=Dimikastafari=- Staging Test wipe, and on which days?

There is no next wipe to predict at -=Dimikastafari=- Staging Test, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 30 days 3 hours.

Server tags

What do the server tags on -=Dimikastafari=- Staging Test mean?

The game's server browser reads the tags -=Dimikastafari=- Staging Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): Slots: 2; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168464 (Build): It runs game build 168464; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does -=Dimikastafari=- Staging Test appear?

You will find -=Dimikastafari=- Staging Test on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How to join

How do you connect to -=Dimikastafari=- Staging Test?

Enter client.connect 80.200.23.239:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp2,ptrak,$r?,v2635,gmrust,cs168464,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp2
Max players Slots: 2.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168464
Build It runs game build 168464.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.