Offline AF 196.46.182.6:28025 checked 43d ago
CORDEX | NO KOS | SOLO, DUO, TRIO
Connect
srv = rust.server("196.46.182.6:28027")
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 8d 18h. # 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:28025
- 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 · 20 on average | 3/150 |
| 1 | ServerZ Rust Monthly ZA | AF · groups of 8+ · monthly · 2 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 · 8 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 · 2 on average | 0/100 |
Quick answers
From the figures on this page.
Population data
What position does CORDEX | NO KOS | SOLO, DUO, TRIO take in the server rankings?
On seven-day player hours CORDEX | NO KOS | SOLO, DUO, TRIO is #9,870 overall and #21 in Africa, inside the top – of all ranked servers.
How full does CORDEX | NO KOS | SOLO, DUO, TRIO run?
Offline now for CORDEX | NO KOS | SOLO, DUO, TRIO, with the last sample 43 days 14 hours ago.
Server facts
What is the Rust version on CORDEX | NO KOS | SOLO, DUO, TRIO?
Version Rust network protocol 2633 and build 163794 on Linux is reported by CORDEX | NO KOS | SOLO, DUO, TRIO. Joining needs the same protocol on your game; Steam handles the update.
Is CORDEX | NO KOS | SOLO, DUO, TRIO up, and what does its uptime show?
Offline now for CORDEX | NO KOS | SOLO, DUO, TRIO, last seen 43 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 13 September 2026.
Where does CORDEX | NO KOS | SOLO, DUO, TRIO sit?
The AF tag is what CORDEX | NO KOS | SOLO, DUO, TRIO uses to list 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:28025 is its address.
Settings and map
Which settings and rules does CORDEX | NO KOS | SOLO, DUO, TRIO run?
You will not find a gather rate in the string CORDEX | NO KOS | SOLO, DUO, TRIO. The group limit sits at the default of 8 players. 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, Valve's anti-cheat, is enabled.
Which map has CORDEX | NO KOS | SOLO, DUO, TRIO selected?
CORDEX | NO KOS | SOLO, DUO, TRIO runs a procedural map, which the game generates.
Wipes and dates
On what schedule does CORDEX | NO KOS | SOLO, DUO, TRIO wipe?
Expect an estimate: CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe is projected from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 47 days 14 hours ago. A monthly wipe schedule is published in its tags.
Tags and filters
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. Under these filters on the server list, it is listed: 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?
Read by the game's server browser, the tags CORDEX | NO KOS | SOLO, DUO, TRIO publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); AF (Africa): Africa is its listing in the server browser. 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.
How to join
How can I connect to CORDEX | NO KOS | SOLO, DUO, TRIO?
The manual route: launch Rust, F1, then client.connect 196.46.182.6:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.