MiniCore Dev
Key statistics
the figures behind the quote- Players now
- 1/ 10 10% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #13,842 top 61%
- Rank · 7d ago
- #9,490 ▼4352 places down
- Last wipe
- 11d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 1 player hours, last seven days
- Map
- – Custom Map
- First seen
- 2 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 61/300 | ▼−38−38.4% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 49/225 | ▼−12−19.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▪+0+0.3% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 17/1000 | ▼−18−50.7% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 10/1000 | ▼−7−41.5% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 17/700 | ▼−42−71.4% |
Quick answers
from the figures on this pageMap and Rules
How is MiniCore Dev configured in terms of rules and settings?
No gather rate appears in the name of MiniCore Dev. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Carbon plugins are running. VAC is active.
Activity
What position does MiniCore Dev hold in the server rankings?
For the last seven days, MiniCore Dev holds rank #13,842 on player hours, in the top 61% of all ranked servers.
What is the population on MiniCore Dev?
At present, MiniCore Dev is offline; the last sighting was 11 days 8 hours ago.
Wipe Schedule
How often does MiniCore Dev wipe?
The record holds too few of MiniCore Dev's wipes to establish its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. 11 days 17 hours ago the current world was created.
Server Info
What is the location of MiniCore Dev?
For MiniCore Dev, no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. 217.217.244.78:28015 is its address.
MiniCore Dev runs which version of Rust?
Rust network protocol 2634 and build 166494 on Windows is what MiniCore Dev runs. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of MiniCore Dev?
Offline at this moment: MiniCore Dev. Last seen 11 days 8 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 2 October 2026.
Tags and Rankings
How should you interpret the tags on MiniCore Dev?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166494 (Build): Build 166494; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^z (Modded): The Modded listing applies: plugins or settings change play; ^y (Carbon): The plugin framework here is Carbon, which MiniCore Dev publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does MiniCore Dev show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature MiniCore Dev: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Joining the Server
What is the process to join MiniCore Dev?
The console route: start Rust, press F1, enter client.connect 217.217.244.78:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y
Game
gmrust
mp10
ts8
v2634
cs166494
ptrak
$r?
Mods and access
^z
^y
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.