Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h.
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
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is CORDEX | NO KOS | SOLO, DUO, TRIO?
You'll see CORDEX | NO KOS | SOLO, DUO, TRIO listed in Africa, tagged AF. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 196.46.182.6:28025.
How reliable is CORDEX | NO KOS | SOLO, DUO, TRIO, and is it up?
You cannot join now: CORDEX | NO KOS | SOLO, DUO, TRIO is offline, last seen 43 days 13 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does CORDEX | NO KOS | SOLO, DUO, TRIO sit?
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.
Resets
When does CORDEX | NO KOS | SOLO, DUO, TRIO wipe, and how often?
The estimate for CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 47 days 13 hours. The tags show a monthly wipe schedule.
Player count
Where does CORDEX | NO KOS | SOLO, DUO, TRIO place in the wider field of Rust servers?
Over the last seven days, CORDEX | NO KOS | SOLO, DUO, TRIO has #9,870 for player hours, in the top – of all ranked servers and #21 in Africa.
Is CORDEX | NO KOS | SOLO, DUO, TRIO a busy server?
The last sighting of CORDEX | NO KOS | SOLO, DUO, TRIO was 43 days 13 hours ago, and it is offline right now.
Tags
What is meant by the tags on CORDEX | NO KOS | SOLO, DUO, TRIO?
The game's browser takes its cue from the tags CORDEX | NO KOS | SOLO, DUO, TRIO has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) provides the plugin framework here; AF (Africa): The server browser lists it under Africa. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does CORDEX | NO KOS | SOLO, DUO, TRIO appear in the Rust Server Score lists and filters?
These Rust Server Score lists count CORDEX | NO KOS | SOLO, DUO, TRIO among them: Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Server rules
What settings and rules apply on CORDEX | NO KOS | SOLO, DUO, TRIO?
The name of CORDEX | NO KOS | SOLO, DUO, TRIO gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. Oxide plugins are running on it. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map CORDEX | NO KOS | SOLO, DUO, TRIO uses?
CORDEX | NO KOS | SOLO, DUO, TRIO runs a procedural map, which the game generates.
Getting in
What is the way to join CORDEX | NO KOS | SOLO, DUO, TRIO?
To connect, start Rust, press F1, and type client.connect 196.46.182.6:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^m,^v,AF,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
AF
AfricaThe server browser lists it under Africa.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
Not enough figures yet to write a report. Check back after a few days on the list.