RUST METRICSFlight deck · live data
Data live Servers11,625 Players41,682 Populated3,017 Fresh wipes 3 h86 Scan5 min
‹ All servers95.143.190.23:35003
Online Full Queue Fresh wipe Wipe due No query

PVE-LiveRust (test)

Online 95.143.190.23:35003 checked 8m ago

biweekly wipes moddedoxidepve
COM 1 · connect
Launch Rust and join

Server instruments

last reading Thu 06:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 127 SERVER FPS

Server fps

48 h low 115 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 72,821 ×1000

Entities

48 h range 44,553–74,872 · memory 2,550 MB
1239 ET SINCE RESTART 04:55

Uptime

4 h 55 min since its last restart, at the last reading
7-day average0peak 3
Rank#5,095top 23%
Last wipe14h agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Memory2,550MB48 h peak 2 players
REC 1

Players
AveragePeakWipe
00.511.5208:0017:0002:0010:0021:0006:00Wiped Wed 28 Oct, 17:02 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance
Server fpsWipe
05010015020008:0017:0002:0010:0021:0006:00Wiped Wed 28 Oct, 17:02 UTCWIPE

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 17 Sep. 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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence

usual gap9.1 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 5.5

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 11hFW
  2. WPT 2Wed 11 Nov, 17:02 UTC13d 9h
  3. WPT 3Wed 25 Nov, 17:02 UTC27d 9h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 11hFW
  5. WPT 5Wed 9 Dec, 17:02 UTC41d 9h

The first 48 hours of its last wipes

Mon 19 OctSat 3 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 17:02 UTC14h ago – – running 1
Mon 19 Oct, 15:29 UTC9d ago 5 halved by day 3 9.1 days 1
Sat 3 Oct, 12:11 UTC25d ago 2 halved by day 8 16.1 days 0
Fri 2 Oct, 15:16 UTC26d ago 2 – 0.9 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What happens on PVE-LiveRust (test) when wipe day comes?

At their busiest, its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 26 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 5.5 when it didn't.

When does PVE-LiveRust (test) wipe?

The prediction follows its tag, because too few of PVE-LiveRust (test)'s wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 14 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

Which tags does PVE-LiveRust (test) carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts30 (Group limit): You may team up with at most 30; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from PVE-LiveRust (test). 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 PVE-LiveRust (test)?

These Rust Metrics lists carry PVE-LiveRust (test): Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.

Occupancy

Where does PVE-LiveRust (test) sit in the rankings?

Ranking for PVE-LiveRust (test): #5,095 on seven-day player hours, top 23% of all ranked servers.

What is the population on PVE-LiveRust (test)?

0 of 100 slots are filled on PVE-LiveRust (test) right now. Seven-day check: 0 players on average. Peak reading: 3. Average at the busiest hour was 2 players, at 19:00 UTC over the last 48 hours.

Server

Where does PVE-LiveRust (test) sit?

Reading: location. PVE-LiveRust (test) gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 95.143.190.23:35003.

What Rust version is PVE-LiveRust (test) on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by PVE-LiveRust (test). Matching protocol is required to join. Let Steam update your game.

What is the performance reading for PVE-LiveRust (test)?

Reading: 150 server fps on average across the last 48 hours. It never dropped below 115. Check: entities. The peak was 74,872, counting buildings, deployables and the rest of the world. Memory peak: 2,868 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is PVE-LiveRust (test) up, and how often does it stay up?

PVE-LiveRust (test) reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 4 hours ago. Reading: 99% uptime over the last 7 full days. It was up 166 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What settings and rules apply on PVE-LiveRust (test)?

Reading the name gives no gather rate for PVE-LiveRust (test). Check: group limit. Up to 30 players. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is PVE-LiveRust (test) on?

Check: map. Procedural, size 3,500, seed 457348898, generated by the game on PVE-LiveRust (test). The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join PVE-LiveRust (test)?

To join: start Rust, press F1 and type client.connect 95.143.190.23:35003. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^p,gmrust,cs168909,ts30,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts30
Group limit You may team up with at most 30.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock 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.