Rust Data

rustdata.spaceservers57.129.14.116:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 57.129.14.116:28015 checked 26d ago

RUST PVE [RU] bete 0.1

moddedoxide

Connect

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

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak –
rank #15,921 # top 70%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

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. 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
15k10k15k20k27 Sep29 Sep2 Oct4 Oct7 Oct9 Oct

Top 70% 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 gap2.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 1 OctThu 1 OctSat 26 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 19:00 UTC FW27d ago 1 NaN running 0
1 Thu 1 Oct, 11:50 UTC27d ago 1 NaN 0.3 days 0
2 Sat 26 Sep, 23:45 UTC32d ago 1 held half 4.5 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
57.129.14.116:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 19:00 UTC
hostname
–
first seen
26 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
1RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average188/225
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average77/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average8/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average22/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 82 on average224/700

Quick answers

From the figures on this page.

Population

How does RUST PVE [RU] bete 0.1 compare in the rankings?

Player hours over seven days put RUST PVE [RU] bete 0.1 at #15,921, in the top 70% of the ranked set.

How full does RUST PVE [RU] bete 0.1 run?

The current row shows RUST PVE [RU] bete 0.1 offline; the last response was 26 days 16 hours ago.

About the server

What is the Rust version on RUST PVE [RU] bete 0.1?

The build is Rust network protocol 2634 and build 166494 on Windows, run by RUST PVE [RU] bete 0.1. The protocol has to match before you can join, and Steam does the updating.

Is RUST PVE [RU] bete 0.1 up, and what does its uptime show?

RUST PVE [RU] bete 0.1 is offline at this refresh; the last response came 26 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 26 September 2026.

Which location does RUST PVE [RU] bete 0.1 run from?

No region tag is published by RUST PVE [RU] bete 0.1, though its name points to Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 57.129.14.116:28015.

Rules, settings, map

What rules and settings are recorded for RUST PVE [RU] bete 0.1?

You will not find a gather rate in the string RUST PVE [RU] bete 0.1. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

Which map has RUST PVE [RU] bete 0.1 loaded?

A procedural map runs on RUST PVE [RU] bete 0.1, generated by the game.

Wipe schedule

When does RUST PVE [RU] bete 0.1 wipe, and on what schedule?

Irregular wipe times on RUST PVE [RU] bete 0.1 leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 16 hours ago.

What is wipe day on RUST PVE [RU] bete 0.1 like?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags and filters

Which Rust Data filters and lists contain RUST PVE [RU] bete 0.1?

These Rust Data lists include RUST PVE [RU] bete 0.1: EU Rust servers and Modded Rust servers. It appears under these filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on RUST PVE [RU] bete 0.1?

These tags are published by RUST PVE [RU] bete 0.1 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.

Join steps

What is the way into RUST PVE [RU] bete 0.1?

Enter client.connect 57.129.14.116:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp500,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players 500 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166494
Build Build number: 166494.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
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 60,549 players 11,720 servers online