Rust Server TrendsSeismic network · station log
Recording Stations11,767 Players80,614 Active3,742 Wipes · 3 h153 48 h

Station XX-15903 · no signal

MiniCore Dev

Offline 217.217.244.19:28015 checked 26d ago

moddedcarbon
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,903
top 70%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15903 · 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
0of 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% 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
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 13:28 UTC26d ago M0.0steady 0 – – 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 · 156 on average
181/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
128/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 89 on average
144/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
20/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
45/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on MiniCore Dev?

No gather rate appears in the name of MiniCore Dev. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on MiniCore Dev right now?

No players are recorded on MiniCore Dev at this moment; it is offline, and the last sighting was 26 days ago.

How does MiniCore Dev rank against other Rust servers?

The last seven days of player hours place MiniCore Dev at #15,903, in the top 70% of all ranked servers.

Server facts

How reliably does MiniCore Dev stay online?

MiniCore Dev is down at the moment; the last recorded contact was 26 days ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 2 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does MiniCore Dev run from?

A region is not published by MiniCore Dev. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 217.217.244.19:28015 is the address it uses.

Which Rust version is MiniCore Dev running?

MiniCore Dev is running Rust network protocol 2634 and build 166494 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on MiniCore Dev?

0 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 26 days 1 hours.

Tags

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 standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running 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?

You will find MiniCore Dev on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Connecting

What steps get you onto MiniCore Dev?

You can connect by pressing F1 in Rust and typing client.connect 217.217.244.19:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166494
Build Game build: 166494.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

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