RUST METRICSFlight deck · live data
Data live Servers11,612 Players35,778 Populated2,872 Fresh wipes 3 h59 Scan5 min
‹ All servers217.217.244.78:28015
Offline Full Queue Fresh wipe Wipe due No query

MiniCore Dev

Offline 217.217.244.78:28015 checked 25d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,842top 61%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

How often does MiniCore Dev wipe, and when?

To tell the rhythm of MiniCore Dev, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 25 days 14 hours ago.

Tags

How should you read the tags on MiniCore Dev?

Tags published by MiniCore Dev, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show MiniCore Dev?

On Rust Metrics, MiniCore Dev sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

What position does MiniCore Dev hold among Rust servers?

Player hours over seven days put MiniCore Dev at #13,842, in the top 61% of all ranked servers.

How full does MiniCore Dev get?

Reading for MiniCore Dev: offline at this moment; last seen 25 days 5 hours ago.

Server details

Where does MiniCore Dev sit?

No region tag on MiniCore Dev. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 217.217.244.78:28015.

What Rust version is MiniCore Dev on?

Reading: MiniCore Dev, Rust network protocol 2634 and build 166494, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is MiniCore Dev, and is it online now?

MiniCore Dev reports offline. The last reading came 25 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Map and rules

How is MiniCore Dev configured, and what rules are in force?

No gather rate appears in the name: MiniCore Dev. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How can you get onto MiniCore Dev?

Check: join. Open Rust, press F1, then enter client.connect 217.217.244.78:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build Build 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins 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.