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.
AveragePeakWipe
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
No rank history yet.
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 14h.
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. You can connect at 196.46.182.6:28015.
Is CORDEX | NO KOS | SOLO, DUO, TRIO up, and how steady is its uptime?
At this moment, CORDEX | NO KOS | SOLO, DUO, TRIO is offline; the last time it was seen was 44 days 14 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is CORDEX | NO KOS | SOLO, DUO, TRIO running?
You will find CORDEX | NO KOS | SOLO, DUO, TRIO on Rust network protocol 2633 and build 163794, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does CORDEX | NO KOS | SOLO, DUO, TRIO reset?
the force wipe gives the basis for estimating CORDEX | NO KOS | SOLO, DUO, TRIO's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 47 days 17 hours have passed since this world was made. The tags show a monthly wipe schedule.
Player numbers
How many players does CORDEX | NO KOS | SOLO, DUO, TRIO usually have?
It has been 44 days 14 hours since CORDEX | NO KOS | SOLO, DUO, TRIO was last seen, and it is offline right now.
Lists and filters
How should you read the tags on CORDEX | NO KOS | SOLO, DUO, TRIO?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): The plugin framework in use is Oxide (uMod); AF (Africa): The server browser lists it under Africa are the tags CORDEX | NO KOS | SOLO, DUO, TRIO publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature CORDEX | NO KOS | SOLO, DUO, TRIO?
These Rust Server Score lists count CORDEX | NO KOS | SOLO, DUO, TRIO among them: Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters 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.
Rules and settings
Which rules does CORDEX | NO KOS | SOLO, DUO, TRIO enforce, and what are its settings?
Nothing in the name of CORDEX | NO KOS | SOLO, DUO, TRIO states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Which map is in play on CORDEX | NO KOS | SOLO, DUO, TRIO?
CORDEX | NO KOS | SOLO, DUO, TRIO runs a procedural map, which the game generates.
Connecting
How do you get onto CORDEX | NO KOS | SOLO, DUO, TRIO?
Enter client.connect 196.46.182.6:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^m,^v,AF,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
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.