Offline 217.217.244.41:28015 checked 28d ago
MiniCore Dev
Connect
srv = rust.server("217.217.244.41:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 17:12 UTC28d ago | 1 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.217.244.41:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 17:12 UTC
- hostname
- –
- first seen
- 29 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 163 on average | 49/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 64/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 60/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 16/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MiniCore Dev rank?
Rank #16,028 on seven-day player hours for MiniCore Dev, within the top 67% of all ranked servers.
What population does MiniCore Dev carry?
Offline now for MiniCore Dev, with the last sample 28 days 1 hours ago.
Server facts
What is the Rust version on MiniCore Dev?
Rust network protocol 2633 and build 165217 on Windows is what MiniCore Dev runs. Steam updates your game for you, but the protocol must match to join.
How reliable is MiniCore Dev, and is it online now?
MiniCore Dev is offline at this refresh; the last response came 28 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 29 September 2026.
Where does MiniCore Dev sit?
No region is published by MiniCore Dev. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 217.217.244.41:28015.
Settings and map
Which settings and rules does MiniCore Dev run?
You will not find a gather rate in the string MiniCore Dev. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on MiniCore Dev?
The game generates its map: procedural, on MiniCore Dev.
Wipe schedule
On what schedule does MiniCore Dev wipe?
Too few wipes are on record for MiniCore Dev to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 28 days 6 hours ago, and that is the one in play.
What is wipe day on MiniCore Dev like?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does MiniCore Dev appear among Rust Data lists and filters?
The Rust Data lists that MiniCore Dev fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on MiniCore Dev?
The game's server browser reads these tags from MiniCore Dev: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join MiniCore Dev?
The manual route: launch Rust, F1, then client.connect 217.217.244.41:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.