Offline 217.217.244.32:28015 checked 27d ago
MiniCore Dev
Connect
srv = rust.server("217.217.244.32: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 63% 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.217.244.32:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 20:42 UTC
- hostname
- –
- first seen
- 1 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 | 52/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 117 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 55/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 12/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 8/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does MiniCore Dev rank?
Rank #14,631 on seven-day player hours for MiniCore Dev, within the top 63% of all ranked servers.
How many players does MiniCore Dev hold at once?
The current row shows MiniCore Dev offline; the last response was 27 days ago.
Server data
What Rust version does MiniCore Dev run?
Version Rust network protocol 2634 and build 166494 on Windows is reported by MiniCore Dev. Steam updates your game for you, but the protocol must match to join.
Is MiniCore Dev up, and what does its uptime show?
Offline now for MiniCore Dev, last seen 27 days ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 1 October 2026.
Which location does MiniCore Dev run from?
There is no region published for 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.32:28015.
Rules, settings, map
What rules and settings are recorded for MiniCore Dev?
The name MiniCore Dev carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. Anti-cheat status: VAC on.
Which map has MiniCore Dev selected?
A procedural map runs on MiniCore Dev, generated by the game.
Wipes and dates
When does MiniCore Dev wipe, and on what schedule?
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. This world was created 27 days 2 hours ago.
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. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on MiniCore Dev hold?
The game's server browser reads these tags from MiniCore Dev: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; 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): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to MiniCore Dev?
Enter client.connect 217.217.244.32:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.