RUST METRICSFlight deck · live data
Data live Servers11,667 Players48,316 Populated3,167 Fresh wipes 3 h118 Scan5 min
‹ All servers217.217.244.42:28015
Offline Full Queue Fresh wipe Wipe due No query

MiniCore Dev

Offline 217.217.244.42:28015 checked 23d 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,941top 71%
Last wipe26d 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 71% 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. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 26 days 19 hours ago.

Lists and filters

How should you read the tags on MiniCore Dev?

Tags published by MiniCore Dev, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; 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): Build 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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.

Occupancy

What position does MiniCore Dev hold among Rust servers?

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

What is the population on MiniCore Dev?

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

Server

Where does MiniCore Dev sit?

Reading: location. MiniCore Dev gives no region. 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.42:28015.

What Rust version is MiniCore Dev on?

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

Is MiniCore Dev up, and how often does it stay up?

MiniCore Dev reports offline. The last reading came 23 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 5 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on MiniCore Dev?

Reading the name gives no gather rate for MiniCore Dev. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

How to join

How do you connect to MiniCore Dev?

Press F1 in Rust and enter client.connect 217.217.244.42:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

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 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 Build 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.