RUST METRICSFlight deck · live data
Data live Servers11,869 Players90,153 Populated3,832 Fresh wipes 3 h374 Scan5 min
‹ All servers146.120.34.119:28015
Offline Full Queue Fresh wipe Wipe due No query

WolframPVP

Offline 146.120.34.119:28015 checked 34d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,578top 66%
Last wipe34d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep27 Sep29 Sep1 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap4.9 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 24 SepSat 19 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 24 Sep, 16:21 UTC34d ago 1 – running 0
Sat 19 Sep, 18:28 UTC39d ago 1 – 4.9 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on WolframPVP when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does WolframPVP follow?

Its rhythm cannot be told from the wipes of WolframPVP on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 34 days 23 hours ago the current world was made.

Tags

Which tags does WolframPVP carry, and what do they mean?

These are the tags WolframPVP publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show WolframPVP?

These Rust Metrics lists carry WolframPVP: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does WolframPVP sit in the rankings?

Player hours over seven days put WolframPVP at #14,578, in the top 66% of all ranked servers.

What player count does WolframPVP carry?

Reading for WolframPVP: offline at this moment; last seen 34 days 22 hours ago.

Server details

Where does WolframPVP sit?

Reading: location. WolframPVP gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 146.120.34.119:28015.

What Rust version is WolframPVP on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by WolframPVP. Check: protocol. To join, your game must match; Steam handles the update.

Is WolframPVP up, and how often does it stay up?

WolframPVP reports offline. The last reading came 34 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 19 September 2026.

Rules and settings

What settings and rules apply on WolframPVP?

No gather rate appears in the name: WolframPVP. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is WolframPVP on?

Check: map. Procedural, generated by the game, on WolframPVP.

How to join

How can you get onto WolframPVP?

Check: join. Open Rust, press F1, then enter client.connect 146.120.34.119:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.