Rust Server TrendsSeismic network · station log
Recording Stations11,752 Players57,724 Active3,422 Wipes · 3 h129 48 h

Station AF-15836 · no signal

CORDEX PVP

Offline AF 156.155.49.105:28015 checked 19d ago

biweekly wipes
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,836
top 72% · #19 in AF
Last wipe
20d ago
biweekly schedule
Next wipe
7d 20h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station AF-15836 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep29 Sep3 Oct12 Oct16 Oct

Top 72% of all ranked servers, top 56% in AF. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

usual gap
5.6 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
0%else halves by day 1.5

Coming wipes

  1. 7d 20hThu 5 Nov, 19:00 UTCFW
  2. 21d 22hThu 19 Nov, 21:49 UTC
  3. 35d 20hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 8 OctThu 24 SepFri 18 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 8 Oct, 21:49 UTC20d ago M0.0steady 0 – running 0
Thu 24 Sep, 09:12 UTC34d ago M0.0rising 1 halved by day 1 14.5 days 0
Fri 18 Sep, 18:38 UTC40d ago M0.0rising 1 halved by day 2 5.6 days 0
Thu 17 Sep, 17:04 UTC41d ago M0.0rising 1 – 1.1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Intoxicated ZA Vanilla 1 - 15 Oct AF · groups of 8+ · biweekly · 7 on average
3/ 100
Intoxicated ZA Vanilla 3 - 01 Oct AF · groups of 8+ · monthly · 19 on average
8/ 150
ServerZ Rust Monthly ZA AF · groups of 8+ · monthly · 1 on average
1/ 50
Voodoo ZA AF · groups of 8+ · monthly · 1 on average
3/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average
80/ 200
Rustafied.com - EU Medium - Large EU · groups of 16+ · biweekly · 133 on average
32/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on CORDEX PVP?

The procedural map on CORDEX PVP is size 3,000 with seed 614225823, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on CORDEX PVP?

The name of CORDEX PVP gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on CORDEX PVP right now?

No players are recorded on CORDEX PVP at this moment; it is offline, and the last sighting was 19 days 11 hours ago.

How does CORDEX PVP rank against other Rust servers?

For player hours across the last seven days, CORDEX PVP takes #15,836 overall and #19 in Africa, inside the top 72% of all ranked servers.

Server details

How reliably does CORDEX PVP stay online?

As recorded now, CORDEX PVP is not reachable, the last contact having been 19 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 16 September 2026.

Which region does CORDEX PVP run from?

The AF tag is how CORDEX PVP lists itself in Africa. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 156.155.49.105:28015 is the address it uses.

Which Rust version is CORDEX PVP running?

CORDEX PVP is running Rust network protocol 2634 and build 167231 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on CORDEX PVP?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 1.5 it fell below half in the wipes where it didn't hold.

On what timetable does CORDEX PVP run its wipes?

Its schedule cannot be confirmed, as too few of CORDEX PVP's wipes are on record; the prediction follows its tag instead. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 20 days. Every two weeks it wipes, according to the schedule in its tags.

Lists and tags

What do the server tags on CORDEX PVP mean?

These are the tags CORDEX PVP publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167231 (Build): Game build: 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; AF (Africa): In the server browser it appears under Africa. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does CORDEX PVP appear?

These Rust Server Trends lists include CORDEX PVP: Rust community servers without the side modes. You will find it under these filters on the server list: Region: Africa; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks.

Join the server

How do you connect to CORDEX PVP?

Enter client.connect 156.155.49.105:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^b,AF,gmrust,cs167231,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167231
Build Game build: 167231.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Region

AF
Africa In the server browser it appears 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.