Rust Server Analytics 69,961 players11,800 servers
All servers
Drill-through Server detail

PVE-LiveRust (test)

Online 95.143.190.23:35003 checked 10m ago

Drill-through
FilterServeris PVE-LiveRust (test)
Attributes
biweekly wipes moddedoxidepve
Last refreshed
Players now 0/ 100
7-day average 0 peak 3
Rank #5,111 top 23%
Last wipe 4h ago biweekly schedule
Next wipe 7d 21h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.511.5222:0007:0016:0000:0009:0020:00Wiped Wed 28 Oct, 17:02 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
05010015020022:0007:0016:0000:0009:0020: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.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. 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

InWhen, UTCKind
7d 21hThu 5 Nov, 19:00 UTCFW force wipe
13d 19hWed 11 Nov, 17:02 UTCits own
27d 19hWed 25 Nov, 17:02 UTCits own
35d 21hThu 3 Dec, 19:00 UTCFW force wipe
41d 19hWed 9 Dec, 17:02 UTCits own

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 17:02 UTC4h ago – – running 1
Mon 19 Oct, 15:29 UTC9d ago 5 – – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 247 on average 246 / 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 237 on average 261 / 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 102 on average 106 / 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 60 on average 20 / 200
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 51 on average 37 / 100
Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid groups of 8+ · biweekly · 50 on average 52 / 250

Quick answers

from the figures on this page

Wipe cycle

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 the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world now in play was created 4 hours ago. A wipe every two weeks is stated in its tags.

On PVE-LiveRust (test), what happens on wipe day?

Recent wipes averaged a busiest count of 3 players. The highest player count on the latest wipe arrived 26 hours in. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. In the other cases the crowd dropped below half by day 5.5.

Server

What is the hosting location of PVE-LiveRust (test)?

No region appears in what PVE-LiveRust (test) publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 95.143.190.23:35003.

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

Rust network protocol 2635 and build 168909 on Linux is the setup for PVE-LiveRust (test). The protocol has to match before you can join; Steam updates it automatically.

Is PVE-LiveRust (test) up, and how steady is its uptime?

The current status of PVE-LiveRust (test) is online. About 3 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 100%, or 168 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.

What performance does PVE-LiveRust (test) show?

Server fps averaged 159 over the last 48 hours, with a floor of 127. Buildings, deployables and all other world objects brought the entity total to 71,987. At its highest, memory use was 2,333 MB. Players experience lag as low fps combined with a rising entity count.

Lists and tags

How should the tags on PVE-LiveRust (test) be read?

The game's server browser reads the tags PVE-LiveRust (test) publishes: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts30 (Group limit): Teams hold no more than 30; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^b (Biweekly): A two-week wipe cycle; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does PVE-LiveRust (test) appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include PVE-LiveRust (test): Modded Rust servers: live data and PvE Rust servers by live population. On the server list, the filters that return it are: 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.

Population

Against other Rust servers, how does PVE-LiveRust (test) compare?

Player hours for the last seven days place PVE-LiveRust (test) at #5,111, in the top 23% of the ranked field.

At what level does PVE-LiveRust (test) run its population?

Of 100 slots, 0 are filled on PVE-LiveRust (test) at this refresh. The seven-day mean is 0 players, against a peak of 3. Across the last 48 hours, 19:00 UTC shows the highest average: 2 players.

Map and rules

What are the settings on PVE-LiveRust (test), and its rules?

Gather rate is not mentioned in the name of PVE-LiveRust (test). A maximum of 30 players per group applies. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. Anti-cheat status: VAC on.

What is the map for PVE-LiveRust (test)?

A procedural map of size 3,500 with seed 457348898, generated by the game, runs on PVE-LiveRust (test). Size and seed fix the map, so a RustMaps view is available from this page.

How to join

How can a player join PVE-LiveRust (test)?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 95.143.190.23:35003.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players 100 slots in total.
ts30
Group limit Teams hold no more than 30.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code The region code is blank.

Wipe schedule

^b
Biweekly A two-week wipe cycle.

Gameplay

^p
PvE No fighting between players, with the world as the threat.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded The Modded section, because plugins or settings modify play.

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.