Offline 217.217.244.52:28015 checked 24d ago
MiniCore Dev
Connect
srv = rust.server("217.217.244.52: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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.217.244.52:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 13:28 UTC
- hostname
- –
- first seen
- 3 Oct 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 · 157 on average | 132/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 117/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 33/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 33/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does MiniCore Dev rank?
Over the last seven days MiniCore Dev sits at #13,893 on player hours, in the top 61% of ranked servers.
How many players does MiniCore Dev hold at once?
MiniCore Dev returns no live count at this refresh, having last been seen 24 days 20 hours ago.
About the server
What is the Rust version on MiniCore Dev?
Rust network protocol 2634 and build 166494 on Windows is what MiniCore Dev runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is MiniCore Dev, and is it online now?
MiniCore Dev is offline at this refresh; the last response came 24 days 20 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 3 October 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. 217.217.244.52:28015 is its address.
Rules, settings, map
Which rules apply on MiniCore Dev, and what settings?
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. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
Wipe schedule
On what schedule does MiniCore Dev wipe?
The record for MiniCore Dev holds too few wipes to show a 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 26 days 7 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold MiniCore Dev, and which filters?
On Rust Data, MiniCore Dev appears in these lists: 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?
These tags are published by MiniCore Dev and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to MiniCore Dev?
In Rust, F1 opens the console: type client.connect 217.217.244.52:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.