RUST METRICSFlight deck · live data
Data live Servers11,893 Players98,350 Populated3,934 Fresh wipes 3 h402 Scan5 min
‹ All servers156.155.49.105:28015
Offline Full Queue Fresh wipe Wipe due No query

CORDEX PVP

Offline AF 156.155.49.105:28015 checked 20d ago

biweekly wipes
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,836top 72% · #19 in AF
Last wipe20d agobiweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

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

usual gap5.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1.5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 1hFW
  2. WPT 2Thu 19 Nov, 21:49 UTC21d 4h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 1hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 21:49 UTC20d ago 0 – running 0
Thu 24 Sep, 09:12 UTC35d ago 1 halved by day 1 14.5 days 0
Fri 18 Sep, 18:38 UTC40d ago 1 halved by day 2 5.6 days 0
Thu 17 Sep, 17:04 UTC42d ago 1 – 1.1 days 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on CORDEX PVP?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1.5 it fell below half.

How often does CORDEX PVP wipe, and when?

Its tag guides the prediction: too few of CORDEX PVP's wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 20 days 18 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tags

Which tags does CORDEX PVP carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Game build reading: 167231; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; AF (Africa): Africa is the browser category it sits in from CORDEX PVP. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does CORDEX PVP appear in Rust Metrics lists and filters?

These Rust Metrics lists carry CORDEX PVP: Rust community servers: live readings. These filters bring it up 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.

Player count

Where does CORDEX PVP sit in the rankings?

Player hours over the last seven days put CORDEX PVP at #15,836, #19 in Africa, in the top 72% of all ranked servers.

What player count does CORDEX PVP carry?

CORDEX PVP is not responding; status offline, last seen 20 days 5 hours ago.

Server details

What location is CORDEX PVP hosted in?

Its AF tag places CORDEX PVP in Africa. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 156.155.49.105:28015.

What Rust version is CORDEX PVP on?

Version check: Rust network protocol 2634 and build 167231 on Windows, run by CORDEX PVP. To get in, your game needs the same protocol; Steam applies the update.

How reliable is CORDEX PVP, and is it online now?

Reading: offline. CORDEX PVP last answered 20 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 September 2026.

Settings and map

How is CORDEX PVP configured, and what rules are in force?

Check: gather rate. The name CORDEX PVP does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is CORDEX PVP on?

From seed 614225823, the game generates the procedural map on CORDEX PVP. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to CORDEX PVP?

To join: start Rust, press F1 and type client.connect 156.155.49.105:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Game build reading: 167231.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Region

AF
Africa Africa is the browser category it sits in.

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.