Statistical profileOnline
milinhadumal
157.85.89.124:28943 checked 2h ago
Connect to this server
1. Main points
Players now
0/ 40
0% full
7-day average
0
peak 5
Rank
#5,659
top 25%
Last wipe
10d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 0 players on it, 0% of its 40 slots.
- Over the last seven days it averaged 0 players, with a peak of 5.
- It ranks #5,659 of all ranked servers, the top 25%, on player hours over the last seven days.
- Its current map went up 10d ago.
2. Players
Figure 1: Players on milinhadumal
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
4
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 17 Oct, 20:55 UTC10d ago | 4 | – | running | 4 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of milinhadumal
3500 · seed 1671266868
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 3500 |
| Seed | 1671266868 |
8. Server characteristics
Table 3: Characteristics of milinhadumal
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 157 on average | 205 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50 / 1000 |
10. Quick answers
From the figures on this page.
Wipe details
On what schedule are wipes carried out on milinhadumal?
Too few wipes of milinhadumal are on record to establish its rhythm. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 10 days 18 hours have passed since this world was made.
What should you expect on wipe day at milinhadumal?
Recent wipes drew an average peak of 4 players. On the latest wipe, 0 hours passed before the crowd peaked.
Server record
What does the record show for the uptime and current status of milinhadumal?
At the latest check, milinhadumal was online. By its own reported uptime, it restarted about 2 days 6 hours ago. A total of 168 of 168 hours were up over 7 full days, which is 100% of the time. The first sighting of it by Rust Census was on 17 October 2026.
What does the performance record of milinhadumal show?
The figures for the last 48 hours give an average of 232 server fps and a minimum of 206. Buildings, deployables and everything else in the world took the entity count to 68,997. The peak memory use recorded was 4,044 MB. Lag, as players feel it, comes from low fps and a climbing entity count.
What location has been recorded for milinhadumal?
No region is given by milinhadumal. Rust Census does not look up where the machine stands; it shows where a server says it is. At 157.85.89.124:28943 it is addressed.
Which Rust version is milinhadumal running?
The version in use on milinhadumal is Rust network protocol 2635 and build 168909 on Linux. Steam updates your game for you, but it has to be on the same protocol to join.
Population
What are the current player figures for milinhadumal?
milinhadumal stands at 0 players from 40 slots in this release. Averaged over seven days: 0 players, with a peak of 5. Over the past 48 hours the highest average fell at 23:00 UTC: 0 players.
In the rankings of Rust servers, where is milinhadumal placed?
The rank for milinhadumal is #5,659 on seven-day player hours, in the top 25% of ranked servers.
Lists and tags
Which Rust Census filters and lists cover milinhadumal?
Included in these Rust Census lists is milinhadumal: Modded Rust servers, counted. 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 carry?
gmrust (Game mode): The game mode is standard survival as Rust runs it; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Plugins or settings alter the game on this modded server are the tags milinhadumal publishes, and the game's server browser reads them. At the top of this page you will find the tags for current players, queue and world creation time.
Settings and map
What map is listed for milinhadumal?
Size 3,500 and seed 1671266868: that is the procedural map on milinhadumal, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.
How is milinhadumal configured, and what rules does it keep?
No gather rate is recorded for milinhadumal in its name. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
How to join
What steps are needed to join milinhadumal?
Enter client.connect 157.85.89.124:28943 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp40 | Max players 40 slots are available. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Plugins or settings alter the game on this modded server. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.