Rust Data

rustdata.spaceservers131.129.135.38:28016.ipynb

Run all rust-data · live

‹ All servers

Online 131.129.135.38:28015 checked 9m ago

VoidOrder_PVEServer

monthly wipes moddedoxidepve

Connect

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

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 1 # peak 12
rank #3,915 # top 18%
last wipe 24d ago # monthly schedule
next wipe 8d 19h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75100:0009:0018:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020000:0009:0018:0003:0012:0021:00

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 5 Oct. 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
12k4k6k8k5 Oct9 Oct14 Oct18 Oct23 Oct27 Oct

Top 18% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 8d 19h. # The force wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

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

Map

4500 · seed 1234567
Map of VoidOrder_PVEServer
map
Procedural Map
size
4500
seed
1234567
Open on RustMaps

Server

srv.info()
address
131.129.135.38:28015
region
–
max players
30
group limit
8, the default
wipe schedule
monthly
last wipe
3 Oct 2026, 07:49 UTC
hostname
–
first seen
5 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 52 on average60/200
1[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 50 on average73/300
2[US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 39 on average42/200
31[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 37 on average23/200
4[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 36 on average21/100
5Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average42/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does VoidOrder_PVEServer rank?

Player hours over seven days put VoidOrder_PVEServer at #3,915, in the top 18% of the ranked set.

How many players does VoidOrder_PVEServer hold at once?

The sample now reads 0 players for VoidOrder_PVEServer, out of 30 slots. Over the last seven days it averaged 1 players and peaked at 12. Peak hour in the last 48 hours: 15:00 UTC, mean 1 players.

Server facts

How smoothly does VoidOrder_PVEServer run?

Averaged over 48 hours: 94 server fps, never under 69. Entity numbers reached 144,935, and that includes buildings, deployables and the rest. The memory field tops out at 4,400 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on VoidOrder_PVEServer?

The build is Rust network protocol 2635 and build 168909 on Windows, run by VoidOrder_PVEServer. Steam updates your game for you, but the protocol must match to join.

How reliable is VoidOrder_PVEServer, and is it up?

VoidOrder_PVEServer reports itself online at the current refresh. The uptime it reports puts the last restart about 3 days 10 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 5 October 2026.

Where does VoidOrder_PVEServer sit?

No region is published by VoidOrder_PVEServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 131.129.135.38:28015 is its address.

Rules, settings, map

What rules and settings are recorded for VoidOrder_PVEServer?

You will not find a gather rate in the string VoidOrder_PVEServer. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has VoidOrder_PVEServer selected?

Size 4,500, seed 1234567: the procedural map on VoidOrder_PVEServer, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does VoidOrder_PVEServer wipe, and how often?

The next wipe for VoidOrder_PVEServer is an estimate, drawn from the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 24 days 15 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.

Tags, lists

Where does VoidOrder_PVEServer appear among Rust Data lists and filters?

These Rust Data lists include VoidOrder_PVEServer: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

How should you read the server tags on VoidOrder_PVEServer?

Read by the game's server browser, the tags VoidOrder_PVEServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): 30 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join VoidOrder_PVEServer?

Enter client.connect 131.129.135.38:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://x.com/s_darts0425.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp30
Max players 30 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 60,289 players 11,750 servers online