Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h107 48 h

Station XX-16028 · no signal

MiniCore Dev

Offline 217.217.244.41:28015 checked 28d ago

moddedcarbon
Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,028
top 67%
Last wipe
29d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16028 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

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

Expected events

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 peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 17:12 UTC29d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
205/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on MiniCore Dev?

A procedural map runs on MiniCore Dev, generated by the game.

Which settings and rules apply on MiniCore Dev?

No gather rate appears in the name of MiniCore Dev. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on MiniCore Dev right now?

MiniCore Dev is not responding at this moment and is offline, last seen 28 days 19 hours ago.

How does MiniCore Dev rank against other Rust servers?

On player hours for the past week, MiniCore Dev sits at #16,028, which puts it inside the top 67% of every ranked server.

Server facts

How reliably does MiniCore Dev stay online?

As recorded now, MiniCore Dev is not reachable, the last contact having been 28 days 19 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 29 September 2026.

Which region does MiniCore Dev run from?

A region is not published by MiniCore Dev. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 217.217.244.41:28015.

Which Rust version is MiniCore Dev running?

MiniCore Dev is running Rust network protocol 2633 and build 165217 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on MiniCore Dev?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does MiniCore Dev run its wipes?

The rhythm of MiniCore Dev cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 29 days 1 hours.

Server tags

What do the server tags on MiniCore Dev mean?

Tags published by MiniCore Dev and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): Game build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does MiniCore Dev appear?

The Rust Server Trends lists that take in MiniCore Dev are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Connecting

What steps get you onto MiniCore Dev?

To join, enter client.connect 217.217.244.41:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build Game build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.