MiniCore Dev
Offline 217.217.244.22:28015 checked 28d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
every wipe as a delivery, newest first- 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.
- ShockRust | Blue | NoLimit 29 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 129 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 30 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 22 / 700
- RustSpain.com | EU Main 5 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 4 / 1000
Quick answers
From the figures on this page.
Player count
Where does MiniCore Dev place among Rust servers?
A seven-day player-hours count places MiniCore Dev at #16,699: the top 70% of every ranked server.
How many players are on MiniCore Dev right now?
At the moment MiniCore Dev is offline, having last been seen 28 days 3 hours ago.
Map and rules
On what map does MiniCore Dev take place?
The game generates the procedural map that MiniCore Dev runs.
What settings and rules should you know for MiniCore Dev?
The name of MiniCore Dev gives no gather rate. The game's default applies: 8 players to a group at most. survival is the mode, gather and build and raid: the standard game. Raiding and PvP are both on. The server browser lists it as Modded, because plugins or settings alter the game. Plugins come from Carbon. VAC, Valve's anti-cheat, is switched on.
Operator and location
What is the location of MiniCore Dev?
There is no region published for MiniCore Dev. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 217.217.244.22:28015 is its address.
What is the uptime of MiniCore Dev, and is it online?
MiniCore Dev is offline at the moment, with the last sighting 28 days 3 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. 30 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is MiniCore Dev using?
Rust network protocol 2633 and build 165217 on Windows is what MiniCore Dev runs. To join, your game must be on the same protocol; Steam handles that update for you.
Map resets
On what schedule does MiniCore Dev reset its map?
Its rhythm cannot yet be told: too few of MiniCore Dev's wipes are on record. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. The world it is running was made 29 days 8 hours.
Tags and listings
Where does MiniCore Dev appear across the Rust Wipe Tracker lists and filters?
These Rust Wipe Tracker lists take MiniCore Dev: Modded Rust servers. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on MiniCore Dev?
gmrust (Game mode): Standard Rust survival is the game mode here; mp10 (Max players): It holds 10 slots; ts8 (Group limit): The game default caps teams at 8; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; ^y (Carbon): It uses Carbon for plugins are the tags MiniCore Dev publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
Getting started
How do you connect to MiniCore Dev?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 217.217.244.22:28015.