Offline AF 196.46.182.6:28015 checked 45d ago
CORDEX | NO KOS | SOLO, DUO, TRIO
Connect
srv = rust.server("196.46.182.6:28017")
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. 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 best
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 16h. # The force wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 196.46.182.6:28015
- region
- AF
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 10 Sep 2026, 10:09 UTC
- hostname
- –
- first seen
- 13 Sep 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 | Intoxicated ZA Vanilla 3 - 01 Oct | AF · groups of 8+ · monthly · 19 on average | 3/150 |
| 1 | ServerZ Rust Monthly ZA | AF · groups of 8+ · monthly · 1 on average | 0/50 |
| 2 | Voodoo ZA | AF · groups of 8+ · monthly · 1 on average | 0/100 |
| 3 | Intoxicated ZA Vanilla 1 - 15 Oct | AF · groups of 8+ · biweekly · 7 on average | 3/100 |
| 4 | KAKGENOEG NO KOS SOLO | DUO | TRIO za | AF · trio · monthly · 2 on average | 0/50 |
| 5 | CORDEX NO KOS, SOLO, DUO, TRIO | AF · trio · monthly · 1 on average | 0/100 |
Quick answers
From the figures on this page.
Player counts
What population does CORDEX | NO KOS | SOLO, DUO, TRIO carry?
The current row shows CORDEX | NO KOS | SOLO, DUO, TRIO offline; the last response was 45 days 13 hours ago.
Server data
What Rust version does CORDEX | NO KOS | SOLO, DUO, TRIO run?
Rust network protocol 2633 and build 163794 on Linux is what CORDEX | NO KOS | SOLO, DUO, TRIO runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is CORDEX | NO KOS | SOLO, DUO, TRIO, and is it up?
The latest sample has CORDEX | NO KOS | SOLO, DUO, TRIO offline, with a last sighting 45 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does CORDEX | NO KOS | SOLO, DUO, TRIO run from?
With its AF tag, CORDEX | NO KOS | SOLO, DUO, TRIO lists itself in Africa. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 196.46.182.6:28015 is its address.
Rules, settings, map
What rules and settings are recorded for CORDEX | NO KOS | SOLO, DUO, TRIO?
You will not find a gather rate in the string CORDEX | NO KOS | SOLO, DUO, TRIO. 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. Raids and player combat are enabled. Community is its browser category. The plugin count is Oxide. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.
Which map has CORDEX | NO KOS | SOLO, DUO, TRIO loaded?
CORDEX | NO KOS | SOLO, DUO, TRIO runs a procedural map, which the game generates.
Wipe schedule
When does CORDEX | NO KOS | SOLO, DUO, TRIO wipe, and on what schedule?
An estimate from the force wipe gives CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 48 days 16 hours ago. The tags list wipes as monthly.
Lists and tags
Which Rust Data filters and lists contain CORDEX | NO KOS | SOLO, DUO, TRIO?
On Rust Data, CORDEX | NO KOS | SOLO, DUO, TRIO appears in these lists: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: 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.
Which meanings do the tags on CORDEX | NO KOS | SOLO, DUO, TRIO hold?
These tags are published by CORDEX | NO KOS | SOLO, DUO, TRIO and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); AF (Africa): In the server browser it sits under Africa. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to CORDEX | NO KOS | SOLO, DUO, TRIO?
Enter client.connect 196.46.182.6:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.