Rust Data

rustdata.spaceservers156.155.49.105:28016.ipynb

Run all rust-data · live

‹ All servers

Offline AF 156.155.49.105:28015 checked 19d ago

CORDEX PVP

biweekly wipes

Connect

srv = rust.server("156.155.49.105:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,836 # top 72% · #19 in AF
last wipe 20d ago # biweekly schedule
next wipe 7d 11h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. # 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

inatkind
07d 11hThu 5 Nov, 19:00 UTCFW force wipe
121d 14hThu 19 Nov, 21:49 UTCwipe
235d 11hThu 3 Dec, 19:00 UTCFW force wipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 8 Oct, 21:49 UTC20d ago 0 NaN running 0
1 Thu 24 Sep, 09:12 UTC34d ago 1 halved by day 1 14.5 days 0
2 Fri 18 Sep, 18:38 UTC40d ago 1 halved by day 2 5.6 days 0
3 Thu 17 Sep, 17:04 UTC41d ago 1 NaN 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.

display(srv.map, srv.info())

Map

3000 · seed 614225823
Map of CORDEX PVP
map
Procedural Map
size
3000
seed
614225823
Open on RustMaps

Server

srv.info()
address
156.155.49.105:28015
region
AF
max players
50
group limit
8, the default
wipe schedule
biweekly
last wipe
8 Oct 2026, 22:18 UTC
hostname
–
first seen
16 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Intoxicated ZA Vanilla 1 - Wipe in a few hoursAF · groups of 8+ · biweekly · 7 on average2/100
1Intoxicated ZA Vanilla 3 - 01 OctAF · groups of 8+ · monthly · 19 on average10/150
2ServerZ Rust Monthly ZAAF · groups of 8+ · monthly · 1 on average0/50
3Voodoo ZAAF · groups of 8+ · monthly · 1 on average1/100
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average91/200
5Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 129 on average11/100

Quick answers

From the figures on this page.

Population data

How does CORDEX PVP compare in the rankings?

Ranked #15,836 on seven-day player hours, CORDEX PVP is #19 in Africa and in the top 72% of all ranked servers.

What population does CORDEX PVP carry?

The current row shows CORDEX PVP offline; the last response was 19 days 19 hours ago.

Server data

Which Rust version is CORDEX PVP on?

Version Rust network protocol 2634 and build 167231 on Windows is reported by CORDEX PVP. Joining needs the same protocol on your game; Steam handles the update.

Is CORDEX PVP up, and what does its uptime show?

CORDEX PVP is offline at this refresh; the last response came 19 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 16 September 2026.

In which location is CORDEX PVP hosted?

With its AF tag, CORDEX PVP lists itself in Africa. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 156.155.49.105:28015.

Rules, settings, map

Which rules apply on CORDEX PVP, and what settings?

You will not find a gather rate in the string CORDEX PVP. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has CORDEX PVP loaded?

Size 3,000, seed 614225823: the procedural map on CORDEX PVP, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

On what schedule does CORDEX PVP wipe?

Too few wipes are on record for CORDEX PVP to confirm its schedule, so the tag drives the prediction. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 20 days 9 hours ago. A fortnightly wipe schedule is published in its tags.

On CORDEX PVP, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.5.

Lists and tags

Where does CORDEX PVP appear among Rust Data lists and filters?

These Rust Data lists include CORDEX PVP: Rust community servers, unfiltered. 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.

Which meanings do the tags on CORDEX PVP hold?

These tags are published by CORDEX PVP and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; AF (Africa): The server browser files it under Africa. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to CORDEX PVP?

The manual route: launch Rust, F1, then client.connect 156.155.49.105:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs167231
Build Recorded game build: 167231.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The cycle is fourteen days.

Region

AF
Africa The server browser files 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.

Rust Data 39,799 players 11,618 servers online