Rust HeatmapInfrared · players
IR live Players43,056 Servers11,700 Warm3,055 Fresh wipes · 3h102 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–10° · slots

MiniCore Dev

Offline 217.217.244.236:28015 checked 25d ago

moddedcarbon
Sp1 · players now 1/ 10
10% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,710
rank
top 69%
26d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 25d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server 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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

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

Bx1Wipe schedule

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

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 155 on average
34 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
135 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 117 on average
34 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 92 on average
28 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 88 on average
3 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
4 / 1000

LogQuick answers

from the figures on this page

Wipe schedule

What is the wipe schedule on MiniCore Dev?

Its rhythm cannot yet be told: too few of MiniCore Dev's wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world it runs now dates from 26 days 11 hours ago.

Population

How busy is MiniCore Dev?

Last seen 25 days 5 hours ago, MiniCore Dev is offline at the moment.

How does MiniCore Dev rank against other Rust servers?

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

Map and rules

What are the rules and settings on MiniCore Dev?

No gather rate appears in the name MiniCore Dev. The group limit is 8 players, which is the game's default. The server runs survival, gather, build and raid in the standard game. Players can fight each other, and raids are allowed. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Carbon. The server has VAC, Valve's anti-cheat, turned on.

About the server

Which version of Rust does MiniCore Dev run?

Rust network protocol 2634 and build 166494 on Windows is what MiniCore Dev runs. To join, your game must match the protocol; Steam handles the update.

Is MiniCore Dev online, and how reliable is it?

Offline at the moment: MiniCore Dev was last seen 25 days 5 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 3 October 2026.

Where is MiniCore Dev located?

No region is published by MiniCore Dev. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 217.217.244.236:28015 is its address.

Tags

Which Rust Heatmap lists and filters include MiniCore Dev?

Modded Rust servers, by live population are the Rust Heatmap lists that MiniCore Dev fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

What do the server tags on MiniCore Dev mean?

The game's server browser reads the tags MiniCore Dev publishes: gmrust (Game mode): Survival in the standard Rust form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): To join, run the same version: game protocol 2634; cs166494 (Build): Build 166494; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. The top of this page also shows the tags for players now, the queue and when the world was made.

Connect

How do I join MiniCore Dev?

Press F1 in Rust to open the console, then enter client.connect 217.217.244.236:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer 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 form.
mp10
Max players Slot count: 10.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol To join, run the same version: game protocol 2634.
cs166494
Build Build 166494.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code The region code is blank.

Mods and access

^z
Modded The game is changed by settings or plugins, so it sits under Modded.
^y
Carbon Carbon provides the plugin framework 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.