Rust Data

rustdata.spaceservers46.173.129.3:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 46.173.129.3:28015 checked 8h ago

PVE 1 TEST

moddedoxide

Connect

srv = rust.server("46.173.129.3:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #10,440 # top 47%
last wipe 9h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123411:0012:00

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. 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 Sep30 Sep7 Oct13 Oct20 Oct27 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 2

The first 48 hours of its last wipes

Thu 22 OctWed 14 OctTue 13 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 10:53 UTC9h ago NaN NaN running 0
1 Thu 22 Oct, 15:45 UTC5d ago 1 NaN NaN 0
2 Wed 14 Oct, 18:22 UTC13d ago 1 held half 7.9 days 0
3 Tue 13 Oct, 23:06 UTC13d ago 1 NaN 0.8 days 0
4 Mon 12 Oct, 16:33 UTC15d ago 1 NaN 1.3 days 0
5 Fri 2 Oct, 12:21 UTC25d ago 1 held half 10.2 days 0
6 Thu 1 Oct, 18:35 UTC FW26d ago 1 NaN 0.7 days 0
7 Thu 1 Oct, 11:45 UTC26d ago 1 NaN 0.3 days 0
8 Wed 30 Sep, 18:58 UTC27d ago 1 NaN 0.7 days 1
9 Mon 28 Sep, 23:25 UTC28d ago 1 NaN 1.8 days 1

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
46.173.129.3:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 10:53 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average168/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average120/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average136/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average34/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average137/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average49/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does PVE 1 TEST rank?

Player hours over seven days put PVE 1 TEST at #10,440, in the top 47% of the ranked set.

What population does PVE 1 TEST carry?

Offline now for PVE 1 TEST, with the last sample 8 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

Server data

What is the Rust version on PVE 1 TEST?

The build is Rust network protocol 2635 and build 168909 on Windows, run by PVE 1 TEST. Joining needs the same protocol on your game; Steam handles the update.

How reliable is PVE 1 TEST, and is it up?

The latest sample has PVE 1 TEST offline, with a last sighting 8 hours ago. Over the last 7 full days the hours up number 34 of 168, 20%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does PVE 1 TEST sit?

No region is published by PVE 1 TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.173.129.3:28015.

Rules, settings, map

Which settings and rules does PVE 1 TEST run?

You will not find a gather rate in the string PVE 1 TEST. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on PVE 1 TEST?

The game generates its map: procedural, on PVE 1 TEST.

Wipes and dates

On what schedule does PVE 1 TEST wipe?

No next wipe can be predicted for PVE 1 TEST, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 9 hours ago, and that is the one in play.

What is wipe day on PVE 1 TEST like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. Otherwise the crowd fell below half by day 2.

Tags, lists

Which lists on Rust Data hold PVE 1 TEST, and which filters?

These Rust Data lists include PVE 1 TEST: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on PVE 1 TEST hold?

The game's server browser reads these tags from PVE 1 TEST: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; modded (Modded): The Modded section lists it, because plugins or settings change the game. 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 PVE 1 TEST?

The manual route: launch Rust, F1, then client.connect 46.173.129.3: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 mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,modded

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.
modded
Modded The Modded section lists it, because plugins or settings change the game.

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 82,249 players 11,849 servers online