LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.
The current map
Saturday 17 October 2026, 20:55 UTC
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.
At their busiest, its recent wipes averaged 4 players. Peak population on the latest wipe came 0 hours after it.
milinhadumal's wipe history is too thin on record to show a rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. This world dates from 10 days 5 hours.
These are the Rust Live Stats lists milinhadumal fits: Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks it appears on the server list.
gmrust (Game mode): Standard survival, in the Rust style; mp40 (Max players): 40 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list milinhadumal publishes for the game's server browser. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
0 of milinhadumal's 40 slots are filled right now. Averaged across seven days, 0 players; the peak was 5. Peak hour over 48 hours: 23:00 UTC, at 0 players on average.
Player hours over seven days put milinhadumal at #5,659, in the top 25% of all ranked servers.
Nothing in the name of milinhadumal states a gather rate. The default applies: 8 players to a group. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. Modded is its browser category, where plugins or settings change the game. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.
milinhadumal runs a game-generated procedural map: size 3,500, seed 1671266868. Same size, same seed, same map: RustMaps has it, reachable from this page.
There is no region from milinhadumal. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 157.85.89.124:28943.
The average server fps was 232 over the last 48 hours; the lowest was 208. Entity count reached 68,997: buildings, deployables and the rest of the world. Memory use peaked at 4,044 MB. Lag, as players feel it, comes from low fps and a rising entity count.
milinhadumal operates on Linux with Rust network protocol 2635 and build 168909. To join, your game must use the same protocol; Steam handles the update for you.
Right now milinhadumal is online. The uptime it reports puts the last restart at about 43 hours ago. It was online for 168 of 168 hours in the last 7 full days, or 100% of the time. On 17 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 157.85.89.124:28943 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.