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.
No daily history yet.
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 Wednesday 4 November, 19:06 UTC, in 6d 0h.
Weekly: 7 days after its last 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
No region is published for CORDEX PVP TRIO. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 156.155.49.105:28015.
How dependable is CORDEX PVP TRIO, and is it online at the moment?
The server is down: CORDEX PVP TRIO is offline now, with the last sighting 42 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 16 September 2026, Rust Server Score saw it for the first time.
Which Rust version is CORDEX PVP TRIO running?
The server CORDEX PVP TRIO is on Rust network protocol 2633 and build 163794 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does CORDEX PVP TRIO reset?
weekly: 7 days after its last wipe gives the basis for estimating CORDEX PVP TRIO's next wipe. It is due to wipe next on Wednesday 4 November at 19:06 UTC. The world it runs now was created 42 days 23 hours. The tags carry a weekly wipe schedule.
Player count
Where does CORDEX PVP TRIO place in the wider field of Rust servers?
In the top – of all ranked servers, CORDEX PVP TRIO sits at #15,507 for player hours over the last seven days.
What does the population on CORDEX PVP TRIO look like?
CORDEX PVP TRIO is offline at the moment; the last time it was seen was 42 days 23 hours ago.
Tags
What is meant by the tags on CORDEX PVP TRIO?
The game's browser takes its cue from the tags CORDEX PVP TRIO has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; 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): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show CORDEX PVP TRIO?
These Rust Server Score lists count CORDEX PVP TRIO among them: Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Weekly ^w and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Weekly.
Server rules
Which rules does CORDEX PVP TRIO enforce, and what are its settings?
The name of CORDEX PVP TRIO gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map CORDEX PVP TRIO uses?
The game generates a procedural map for CORDEX PVP TRIO.
How to join
What is the way to join CORDEX PVP TRIO?
To connect, start Rust, press F1, and type client.connect 156.155.49.105:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^w,^v,gmrust,cs163794,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
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.