Offline 5.18.144.106:28015 checked 10d ago
Local PVE | Closed test
Connect
srv = rust.server("5.18.144.106:28017")
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. 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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 5.18.144.106:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 10:24 UTC
- hostname
- –
- first seen
- 19 Oct 2026
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 · 252 on average | 263/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 236/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 105 on average | 83/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 17/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 63/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 0/100 |
Quick answers
From the figures on this page.
Player counts
What position does Local PVE | Closed test take in the server rankings?
Player hours over seven days put Local PVE | Closed test at #15,308, in the top 70% of the ranked set.
How full does Local PVE | Closed test run?
The current row shows Local PVE | Closed test offline; the last response was 10 days 11 hours ago.
About the server
What is the Rust version on Local PVE | Closed test?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Local PVE | Closed test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Local PVE | Closed test, and is it up?
Local PVE | Closed test is offline at this refresh; the last response came 10 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 October 2026.
In which location is Local PVE | Closed test hosted?
No region is published by Local PVE | Closed test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 5.18.144.106:28015.
Rules, settings, map
Which rules apply on Local PVE | Closed test, and what settings?
No gather rate appears in the name: Local PVE | Closed test. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Local PVE | Closed test?
Local PVE | Closed test runs a procedural map, which the game generates.
Wipe schedule
When does Local PVE | Closed test wipe, and how often?
The record for Local PVE | Closed test holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 10 days 11 hours ago.
Tags and filters
Which lists on Rust Data hold Local PVE | Closed test, and which filters?
The Rust Data lists that Local PVE | Closed test fits are: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Local PVE | Closed test?
Read by the game's server browser, the tags Local PVE | Closed test publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into Local PVE | Closed test?
Enter client.connect 5.18.144.106:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.