Live coverage · AF
Offline CORDEX | NO KOS | SOLO, DUO, TRIO is not on the server list right now. The figures below are from when it was last seen, 45d ago.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h. The force wipe
This server has not put up a new map since the desk started watching it.
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.
Estimating CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe relies on the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. The world you are playing on was built 48 days 9 hours. A monthly wipe schedule is published in its tags.
On Rust Live Stats, CORDEX | NO KOS | SOLO, DUO, TRIO is listed under Live Rust community servers and Vanilla Rust servers, live. These filters on the server list bring it up: Region: Africa; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
The server browser reads gmrust (Game mode): Standard survival, in the Rust style; mp100 (Max players): The slot count is 100; ts8 (Group limit): Team cap: 8, which is the game default; v2633 (Protocol): The server runs protocol 2633, so match that version to join; cs163794 (Build): Build: 163794; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^v (Vanilla): It runs the game as Facepunch ships it: rates, kits and rules unchanged; ^o (Oxide): Plugin framework: Oxide (uMod); AF (Africa): The server browser places this server under Africa, which CORDEX | NO KOS | SOLO, DUO, TRIO publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Last seen 45 days 6 hours ago, CORDEX | NO KOS | SOLO, DUO, TRIO is offline right now.
No gather rate appears in the name CORDEX | NO KOS | SOLO, DUO, TRIO. Eight players per group, which is the game's default. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. You find it under Community in the server browser. Plugins run here: Oxide. By its own label it is vanilla: it runs the game as Facepunch ships it: rates, kits and rules unchanged. Anti-cheat: VAC from Valve is enabled.
CORDEX | NO KOS | SOLO, DUO, TRIO uses a procedural map, which the game generates.
Its AF tag places CORDEX | NO KOS | SOLO, DUO, TRIO in Africa. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. Connect to 196.46.182.6:28015.
Rust network protocol 2633 and build 163794 on Linux is what CORDEX | NO KOS | SOLO, DUO, TRIO runs. To join, your game must use the same protocol; Steam handles the update for you.
CORDEX | NO KOS | SOLO, DUO, TRIO is currently offline, with its last appearance 45 days 6 hours ago. It was online for 0 of 168 hours in the last 7 full days, or 0% of the time. On 13 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 196.46.182.6:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.