Online 157.85.89.124:28943 checked 2h ago
milinhadumal
Connect
srv = rust.server("157.85.89.124:28944")
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, measured since 17 Oct. 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 25% 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 4, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 20:55 UTC10d ago | 4 | NaN | running | 4 |
# 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
3500 · seed 1671266868
- map
- Procedural Map
- size
- 3500
- seed
- 1671266868
Server
srv.info()- address
- 157.85.89.124:28943
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 01:34 UTC
- hostname
- –
- first seen
- 17 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 | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does milinhadumal rank?
Over the last seven days milinhadumal sits at #5,659 on player hours, in the top 25% of ranked servers.
How many players does milinhadumal hold at once?
Current row: 0 players on milinhadumal, against 40 slots. Over the last seven days it averaged 0 players and peaked at 5. Peak hour in the last 48 hours: 23:00 UTC, mean 0 players.
Server facts
How smoothly does milinhadumal run?
The 48-hour average is 232 server fps, with a low of 206. Buildings, deployables and all else in the world took the count as high as 68,997 entities. The memory field tops out at 4,044 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is milinhadumal on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by milinhadumal. Joining needs the same protocol on your game; Steam handles the update.
How reliable is milinhadumal, and is it up?
Online is the state at the latest refresh for milinhadumal. A restart about 2 days 6 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 17 October 2026.
In which location is milinhadumal hosted?
No region is published by milinhadumal. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 157.85.89.124:28943.
Rules, settings, map
What rules and settings are recorded for milinhadumal?
The name milinhadumal carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has milinhadumal selected?
milinhadumal runs a procedural map of size 3,500 with seed 1671266868, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does milinhadumal wipe?
The record for milinhadumal holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 10 days 17 hours ago.
What is wipe day on milinhadumal like?
Across recent wipes the busiest point averaged 4 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does milinhadumal appear among Rust Data lists and filters?
These Rust Data lists include milinhadumal: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on milinhadumal hold?
Read by the game's server browser, the tags milinhadumal publishes are: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 into milinhadumal?
In Rust, F1 opens the console: type client.connect 157.85.89.124:28943. Launch Rust on this page does the same by opening the game through Steam and connecting.