RUST METRICSFlight deck · live data
Data live Servers11,674 Players54,186 Populated3,387 Fresh wipes 3 h89 Scan5 min
‹ All servers217.217.244.52:28015
Offline Full Queue Fresh wipe Wipe due No query

MiniCore Dev

Offline 217.217.244.52:28015 checked 24d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

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,893top 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
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 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?

Its rhythm cannot be told from the wipes of MiniCore Dev on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 25 days 20 hours ago.

Tags

Which tags does MiniCore Dev carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): The server runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Carbon handles the plugins here from MiniCore Dev. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Rust Metrics lists featuring 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

What position does MiniCore Dev hold among Rust servers?

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

What player count does MiniCore Dev carry?

MiniCore Dev is not responding; status offline, last seen 24 days 10 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. Check: address. It reads 217.217.244.52:28015.

What Rust version is MiniCore Dev on?

Version check: Rust network protocol 2634 and build 166494 on Windows, run by MiniCore Dev. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on MiniCore Dev, and is it online?

MiniCore Dev reports offline. The last reading came 24 days 10 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 3 October 2026.

Settings and map

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

Check: gather rate. The name MiniCore Dev does not state one. 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. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join MiniCore Dev?

To join: start Rust, press F1 and type client.connect 217.217.244.52:28015. Or press Launch Rust here and Steam opens the game 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 The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build The server runs game build 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^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.