RUST METRICSFlight deck · live data
Data live Servers11,762 Players65,727 Populated3,483 Fresh wipes 3 h193 Scan5 min
‹ All servers217.217.244.19:28015
Offline Full Queue Fresh wipe Wipe due No query

MiniCore Dev

Offline 217.217.244.19:28015 checked 26d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

0% 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#15,903top 70%
Last wipe26d agono schedule published
Next wipe–too few wipes 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 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

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.

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.

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 timing

What should you expect from wipe day on MiniCore Dev?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does MiniCore Dev follow?

To tell the rhythm of MiniCore Dev, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 26 days 22 hours ago the current world was made.

Tags

How should you read the tags on MiniCore Dev?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from MiniCore Dev. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MiniCore Dev appear in Rust Metrics lists and filters?

These Rust Metrics lists carry MiniCore Dev: 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

Where does MiniCore Dev sit in the rankings?

Player hours over seven days put MiniCore Dev at #15,903, in the top 70% of all ranked servers.

How full does MiniCore Dev get?

MiniCore Dev is not responding; status offline, last seen 26 days 22 hours ago.

Operator and location

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. The endpoint you need is 217.217.244.19:28015.

What Rust version is MiniCore Dev on?

Version check: Rust network protocol 2634 and build 166494 on Windows, run by MiniCore Dev. 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 26 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 2 October 2026.

Rules and settings

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

No gather rate appears in the name: MiniCore Dev. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

Connection

How can you get onto MiniCore Dev?

Check: join. Open Rust, press F1, then enter client.connect 217.217.244.19: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 The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Game build reading: 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. 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.