CORDEX | NO KOS | SOLO, DUO, TRIO
Offline AF 196.46.182.6:28025 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
1% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 9h. The force wipe
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 6/150
- 0/50
- 0/100
- 3/100
- 0/50
- 0/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does CORDEX | NO KOS | SOLO, DUO, TRIO follow?
An estimate from the force wipe gives CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 47 days 23 hours ago. The tags state a wipe schedule of one wipe a month.
Tags
How should you read the tags on CORDEX | NO KOS | SOLO, DUO, TRIO?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): It runs Oxide, also known as uMod; AF (Africa): Its browser listing: Africa from CORDEX | NO KOS | SOLO, DUO, TRIO. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show CORDEX | NO KOS | SOLO, DUO, TRIO?
These Rust Metrics lists carry CORDEX | NO KOS | SOLO, DUO, TRIO: Rust community servers: live readings and Vanilla Rust servers, live. Reading: server list filters. It comes up under 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.
Player count
What position does CORDEX | NO KOS | SOLO, DUO, TRIO hold among Rust servers?
Top – of all ranked servers: CORDEX | NO KOS | SOLO, DUO, TRIO takes #9,870 on seven-day player hours and #21 in Africa.
How full does CORDEX | NO KOS | SOLO, DUO, TRIO get?
Status for CORDEX | NO KOS | SOLO, DUO, TRIO: offline. Last seen 43 days 23 hours ago.
Server
Which location does CORDEX | NO KOS | SOLO, DUO, TRIO run from?
Reading: location. The AF tag puts CORDEX | NO KOS | SOLO, DUO, TRIO in Africa. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 196.46.182.6:28025.
What Rust version is CORDEX | NO KOS | SOLO, DUO, TRIO on?
Reading: CORDEX | NO KOS | SOLO, DUO, TRIO, Rust network protocol 2633 and build 163794, Linux. Check: protocol. To join, your game must match; Steam handles the update.
Is CORDEX | NO KOS | SOLO, DUO, TRIO up, and how often does it stay up?
Check: connection. CORDEX | NO KOS | SOLO, DUO, TRIO is offline at this moment. Last contact was 43 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is CORDEX | NO KOS | SOLO, DUO, TRIO configured, and what rules are in force?
Reading the name gives no gather rate for CORDEX | NO KOS | SOLO, DUO, TRIO. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Plugin count: Oxide. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. VAC is on. That is Valve's anti-cheat.
What map is CORDEX | NO KOS | SOLO, DUO, TRIO on?
The game generates a procedural map for CORDEX | NO KOS | SOLO, DUO, TRIO.
How to join
How do you connect to CORDEX | NO KOS | SOLO, DUO, TRIO?
Check: join. Open Rust, press F1, then enter client.connect 196.46.182.6:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.