Online 95.143.190.23:35003 checked 12m ago
PVE-LiveRust (test)
Connect
srv = rust.server("95.143.190.23:35005")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 23% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 16h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 14h | Wed 11 Nov, 17:02 UTC | wipe |
| 2 | 27d 14h | Wed 25 Nov, 17:02 UTC | wipe |
| 3 | 35d 16h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 14h | Wed 9 Dec, 17:02 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 26 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 17:02 UTC9h ago | NaN | NaN | running | 1 |
| 1 | Mon 19 Oct, 15:29 UTC9d ago | 5 | halved by day 3 | 9.1 days | 1 |
| 2 | Sat 3 Oct, 12:11 UTC25d ago | 2 | halved by day 8 | 16.1 days | 0 |
| 3 | Fri 2 Oct, 15:16 UTC26d ago | 2 | NaN | 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.
display(srv.map, srv.info())
Map
3500 · seed 457348898
- map
- Procedural Map
- size
- 3500
- seed
- 457348898
Server
srv.info()- address
- 95.143.190.23:35003
- region
- –
- max players
- 100
- group limit
- 30 max
- wipe schedule
- biweekly
- last wipe
- 28 Oct 2026, 17:02 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 249 on average | 308/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 240 on average | 112/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 104 on average | 181/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 60 on average | 32/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 9/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 49 on average | 54/250 |
Quick answers
From the figures on this page.
Player counts
What position does PVE-LiveRust (test) take in the server rankings?
Rank #5,099 on seven-day player hours for PVE-LiveRust (test), within the top 23% of all ranked servers.
What population does PVE-LiveRust (test) carry?
PVE-LiveRust (test) reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 3. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 2 players.
Server data
What does performance look like on PVE-LiveRust (test)?
The 48-hour average is 155 server fps, with a low of 117. The entity count peaked at 74,872, covering buildings, deployables and the rest of the world. Memory peaked at 2,648 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does PVE-LiveRust (test) run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by PVE-LiveRust (test). Joining needs the same protocol on your game; Steam handles the update.
How reliable is PVE-LiveRust (test), and is it up?
The current sample puts PVE-LiveRust (test) online. Count back 7 hours from its reported uptime to get the last restart. 166 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does PVE-LiveRust (test) sit?
No region is published by PVE-LiveRust (test). Rust Data does not look up where the machine stands; it shows where a server says it is. 95.143.190.23:35003 is its address.
Settings and map
Which rules apply on PVE-LiveRust (test), and what settings?
You will not find a gather rate in the string PVE-LiveRust (test). 30 players is the maximum per group. Game mode pve, with this note: no combat between players. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has PVE-LiveRust (test) selected?
The game generates the map on PVE-LiveRust (test): procedural, size 3,500, seed 457348898. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does PVE-LiveRust (test) wipe, and how often?
The tag sets the prediction: PVE-LiveRust (test) has too few wipes on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 9 hours ago. Its tags carry a wipe schedule of every two weeks.
What is wipe day on PVE-LiveRust (test) like?
The average peak over recent wipes is 3 players. 26 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 5.5.
Tags, lists
Which lists on Rust Data hold PVE-LiveRust (test), and which filters?
These Rust Data lists include PVE-LiveRust (test): Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: 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.
Which meanings do the tags on PVE-LiveRust (test) hold?
Read by the game's server browser, the tags PVE-LiveRust (test) publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts30 (Group limit): Team size tops out at 30; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): Two weeks between wipes; ^p (PvE): PvE: the world is the threat, not other players; ^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.
How to join
How can I connect to PVE-LiveRust (test)?
The manual route: launch Rust, F1, then client.connect 95.143.190.23:35003. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.