Rust Data

rustdata.spaceservers2.58.214.113:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 2.58.214.113:28015 checked 7d ago

wetrixxx+uhs

moddedoxidepve

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,400 # top 69%
last wipe 24d 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, measured since 29 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
15k10k15k20k29 Sep5 Oct10 Oct16 Oct21 Oct27 Oct

Top 69% 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 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 3 OctWed 30 SepTue 29 Sep
01234+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 Sat 3 Oct, 14:13 UTC24d ago 0 NaN running 0
1 Wed 30 Sep, 03:58 UTC27d ago 0 NaN 3.4 days 0
2 Tue 29 Sep, 14:38 UTC28d ago 1 NaN 0.6 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

4500 · seed 6738
Map of wetrixxx+uhs
map
Procedural Map
size
4500
seed
6738
Open on RustMaps

Server

srv.info()
address
2.58.214.113:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
3 Oct 2026, 18:24 UTC
hostname
–
first seen
29 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 244 on average308/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 233 on average226/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 96 on average151/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average16/200
4Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 53 on average52/250
5TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 53 on average23/100

Quick answers

From the figures on this page.

Player counts

What position does wetrixxx+uhs take in the server rankings?

Player hours over seven days put wetrixxx+uhs at #15,400, in the top 69% of the ranked set.

How full does wetrixxx+uhs run?

wetrixxx+uhs returns no live count at this refresh, having last been seen 7 days 1 hours ago. Over the last seven days it averaged 0 players.

About the server

What is the Rust version on wetrixxx+uhs?

Rust network protocol 2634 and build 167781 on Linux is what wetrixxx+uhs runs. The protocol has to match before you can join, and Steam does the updating.

Is wetrixxx+uhs up, and what does its uptime show?

The latest sample has wetrixxx+uhs offline, with a last sighting 7 days 1 hours ago. Uptime of 3% across the last 7 full days: 5 hours of 168. The first row Rust Data holds for it is dated 29 September 2026.

Where does wetrixxx+uhs sit?

There is no region published for wetrixxx+uhs. Rust Data does not look up where the machine stands; it shows where a server says it is. 2.58.214.113:28015 is its address.

Rules, settings, map

Which rules apply on wetrixxx+uhs, and what settings?

The name wetrixxx+uhs carries no gather rate. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. The VAC field reads off.

What is the map on wetrixxx+uhs?

wetrixxx+uhs runs a procedural map of size 4,500 with seed 6738, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

On what schedule does wetrixxx+uhs wipe?

No next wipe can be predicted for wetrixxx+uhs, 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 24 days 4 hours ago, and that is the one in play.

What is wipe day on wetrixxx+uhs like?

Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.

Lists and tags

Which lists on Rust Data hold wetrixxx+uhs, and which filters?

The Rust Data lists that wetrixxx+uhs fits are: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on wetrixxx+uhs?

Read by the game's server browser, the tags wetrixxx+uhs publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 wetrixxx+uhs?

In Rust, F1 opens the console: type client.connect 2.58.214.113:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8,^o^z

Game

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

Gameplay

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

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 61,690 players 11,757 servers online