Rust Data LabData lab · live
Live readings Servers11,718 Players47,661 Populated3,204 Fresh wipes · 3h101 Sampled every 5 min

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

MiniCore Dev

Offline 217.217.244.19:28015 checked 26d ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak –
Rank · atomic number#15,903top 70%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

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

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 13:28 UTC26d ago 0 – running 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… 4
    ShockRust | Blue | NoLimit no group limit · 156 on average 4/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 129
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 129/ 100
  3. 3 Re RETRO RUST #1 … 50
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average 50/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 38
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average 38/ 700
  5. 5 Ru RustSpain.com … 6
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 6/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 5
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 5/ 1,000

Quick answers

from the figures on this page

Map and rules

What rules has MiniCore Dev set, and what settings are in force?

The name of MiniCore Dev carries no 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. Raids and player fights are part of play here. The server browser lists it under Modded, where plugins or settings change the game. Plugins in use: Carbon. The VAC anti-cheat from Valve is enabled.

Server facts

What region hosts MiniCore Dev?

No region is published by MiniCore Dev. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 217.217.244.19:28015 is the address it uses.

On what Rust version does MiniCore Dev operate?

Rust network protocol 2634 and build 166494 on Windows is what MiniCore Dev uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does MiniCore Dev stay online?

MiniCore Dev is not online at the moment; the last sighting was 26 days 10 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. It first appeared to Rust Data Lab on 2 October 2026.

Wipes and resets

What is the wiping pattern on MiniCore Dev?

Too few wipes are on record for MiniCore Dev to reveal a rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 26 days 10 hours ago.

How does MiniCore Dev look on the day of a wipe?

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

Tags, lists

How should you read the tags on MiniCore Dev?

These are the tags MiniCore Dev makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Player slots: 10; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): The server runs protocol 2634, so your game needs the same version; cs166494 (Build): It runs build 166494; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^z (Modded): Because plugins or settings change the game, it is filed under Modded; ^y (Carbon): This server uses the Carbon plugin framework. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does MiniCore Dev appear in?

These themed Rust Data Lab lists carry MiniCore Dev: Modded Rust servers, measured. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Player counts

Against other Rust servers, where does MiniCore Dev place?

The seven-day player-hours table has MiniCore Dev at #15,903, in the top 70% of ranked servers.

How full is MiniCore Dev right now?

MiniCore Dev is offline at the moment; the last sighting was 26 days 10 hours ago.

How to join

What is the way to join MiniCore Dev?

In Rust, press F1 and enter client.connect 217.217.244.19:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players Player slots: 10.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol The server runs protocol 2634, so your game needs the same version.
cs166494
Build It runs build 166494.
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 Because plugins or settings change the game, it is filed under Modded.
^y
Carbon This server uses the Carbon plugin framework.

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.