Rust Data LabData lab · live
Live readings Servers11,611 Players34,878 Populated2,847 Fresh wipes · 3h62 Sampled every 5 min

Element card · group Modded · atomic number 15,326, its rank

-=Dimikastafari=- Staging Test

Offline 80.200.23.239:28015 checked 8d ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 2 0% full Room to join
7-day average0peak –
Rank · atomic number#15,326top 69%
Last wipe29d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

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 gap0.5 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 21:51 UTC29d ago 2 – running 1
Mon 28 Sep, 09:17 UTC29d ago 2 – 0.5 days 0
Sun 27 Sep, 21:20 UTC30d ago 2 – 0.5 days 0

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

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 44
    ShockRust | Blue | NoLimit no group limit · 159 on average 44/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 125
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 125/ 100
  3. 3 Re RETRO RUST #1 … 53
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average 53/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 22
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average 22/ 700
  5. 5 Ru RustSpain.com … 4
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 4/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 6
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 6/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on -=Dimikastafari=- Staging Test?

A procedural map runs on -=Dimikastafari=- Staging Test, generated by the game.

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

Nothing in the name of -=Dimikastafari=- Staging Test gives a gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. You can fight other players and raid them. In the server browser it sits under Modded: the game is changed by plugins or settings. The plugin count is Carbon. The VAC anti-cheat from Valve is enabled.

Server details

What region hosts -=Dimikastafari=- Staging Test?

No region is published by -=Dimikastafari=- Staging Test. Rust Data Lab shows a server's stated location, not a verified position of the machine. Connect at 80.200.23.239:28015.

Which Rust version is -=Dimikastafari=- Staging Test on?

On Windows, -=Dimikastafari=- Staging Test is running Rust network protocol 2635 and build 168464. The protocol must match for you to join; Steam will update your game.

How dependable is -=Dimikastafari=- Staging Test for staying online?

-=Dimikastafari=- Staging Test is not online at the moment; the last sighting was 8 days 6 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. The first sighting by Rust Data Lab was on 27 September 2026.

Wipes and resets

What is the wiping pattern on -=Dimikastafari=- Staging Test?

With no fixed rhythm, -=Dimikastafari=- Staging Test wipes at irregular times, so the next wipe cannot be predicted. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 29 days 6 hours ago.

On -=Dimikastafari=- Staging Test, what happens when wipe day arrives?

Averaged across its recent wipes, the busiest point drew 2 players. The latest wipe's peak fell 4 hours after it began.

Where it appears

What should you understand from the tags -=Dimikastafari=- Staging Test carries?

gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Player slots: 2; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168464 (Build): It runs build 168464; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^z (Modded): Plugins or settings alter the game, so it lists under Modded; ^y (Carbon): The plugin framework here is Carbon: that is the tag list -=Dimikastafari=- Staging Test publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does -=Dimikastafari=- Staging Test appear in?

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

Population

How does -=Dimikastafari=- Staging Test compare with other servers in the rankings?

-=Dimikastafari=- Staging Test sits at #15,326 for seven-day player hours, placing it in the top 69% of ranked servers.

How full is -=Dimikastafari=- Staging Test right now?

The last recorded sighting of -=Dimikastafari=- Staging Test was 8 days 6 hours ago, and it is offline now.

Connection

What is the way to join -=Dimikastafari=- Staging Test?

Open the console with F1 in Rust and type client.connect 80.200.23.239:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp2
Max players Player slots: 2.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168464
Build It runs build 168464.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

Mods and access

^z
Modded Plugins or settings alter the game, so it lists under Modded.
^y
Carbon The plugin framework here is Carbon.

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.