NAM | Why Oh Why | Mindless Choas KOS allowed
Offline 41.63.239.4:28015 checked 4d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 25 Oct, 09:07 UTC4d ago | 1 | – | running | 0 |
| Fri 2 Oct, 15:58 UTC27d ago | 1 | held half | 22.7 days | 0 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 151 on average | 13 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 35 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 4 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 21 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 123 / 200 |
Quick answers
from the figures on this pageWipe cycle
On what cycle does NAM | Why Oh Why | Mindless Choas KOS allowed wipe?
The rhythm of NAM | Why Oh Why | Mindless Choas KOS allowed cannot yet be told: too few of its wipes are on record. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The current world dates from 4 days 16 hours.
On NAM | Why Oh Why | Mindless Choas KOS allowed, what happens on wipe day?
The average busiest count over recent wipes is 1 players. The highest player count on the latest wipe arrived 0 hours in. Above half that peak until the next wipe held in 100% of recent wipes.
Server
Which location hosts NAM | Why Oh Why | Mindless Choas KOS allowed?
A region is not published by NAM | Why Oh Why | Mindless Choas KOS allowed. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 41.63.239.4:28015.
What Rust build does NAM | Why Oh Why | Mindless Choas KOS allowed run?
Rust network protocol 2635 and build 168909 on Linux is the setup for NAM | Why Oh Why | Mindless Choas KOS allowed. Your game must match the protocol to join, and Steam applies that update.
What uptime does NAM | Why Oh Why | Mindless Choas KOS allowed show, and is it up?
Last seen 4 days 7 hours ago, NAM | Why Oh Why | Mindless Choas KOS allowed now reports offline. Of 168 hours in the last 7 full days, 10 were up: 6%. 29 September 2026 is when Rust Server Analytics first recorded it.
Lists and tags
How should the tags on NAM | Why Oh Why | Mindless Choas KOS allowed be read?
Tags from NAM | Why Oh Why | Mindless Choas KOS allowed, as read by the game's server browser, are: gmrust (Game mode): Rust survival, standard ruleset; mp40 (Max players): 40 slots in total; ts0 (Group limit): Teams are not enabled; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing, where plugins or settings change the game. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does NAM | Why Oh Why | Mindless Choas KOS allowed appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count NAM | Why Oh Why | Mindless Choas KOS allowed among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last week.
Player numbers
What position does NAM | Why Oh Why | Mindless Choas KOS allowed hold in the server rankings?
On player hours over seven days, NAM | Why Oh Why | Mindless Choas KOS allowed ranks #13,999, within the top 63% of ranked servers.
At what level does NAM | Why Oh Why | Mindless Choas KOS allowed run its population?
NAM | Why Oh Why | Mindless Choas KOS allowed is offline at this refresh; the last contact was 4 days 7 hours ago. The seven-day mean is 0 players, against a peak of 1.
Map and rules
What settings and rules does NAM | Why Oh Why | Mindless Choas KOS allowed use?
Gather rate is not mentioned in the name of NAM | Why Oh Why | Mindless Choas KOS allowed. Group limit: not published. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for NAM | Why Oh Why | Mindless Choas KOS allowed?
NAM | Why Oh Why | Mindless Choas KOS allowed uses a procedural map of size 4,500 with seed 13698755, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here.
Connection
How do you connect to NAM | Why Oh Why | Mindless Choas KOS allowed?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 41.63.239.4:28015.