Offline 107.136.237.168:28015 checked 20d ago
Solo PVE
Connect
srv = rust.server("107.136.237.168: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 · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 16:20 UTC20d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 107.136.237.168:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 21:14 UTC
- hostname
- –
- first seen
- 8 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 · 248 on average | 282/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 238 on average | 215/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 103 on average | 126/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 60 on average | 14/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 53 on average | 61/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 51 on average | 18/100 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Solo PVE rank?
Rank #15,541 on seven-day player hours for Solo PVE, within the top 70% of all ranked servers.
How full does Solo PVE run?
Solo PVE returns no live count at this refresh, having last been seen 20 days 1 hours ago.
About the server
Which Rust version is Solo PVE on?
The build is Rust network protocol 2634 and build 167231 on Windows, run by Solo PVE. Steam updates your game for you, but the protocol must match to join.
How reliable is Solo PVE, and is it online now?
Offline now for Solo PVE, last seen 20 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 8 October 2026.
In which location is Solo PVE hosted?
No region is published by Solo PVE. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 107.136.237.168:28015.
Rules, settings, map
What rules and settings are recorded for Solo PVE?
The name Solo PVE carries no gather rate. The group limit sits at the default of 8 players. Game mode pve, with this note: no combat between players. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
What is the map on Solo PVE?
The game generates its map: procedural, on Solo PVE.
Wipe schedule
When does Solo PVE wipe, and on what schedule?
Too few wipes are on record for Solo PVE to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 20 days 1 hours ago, and that is the one in play.
On Solo PVE, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 2 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold Solo PVE, and which filters?
These Rust Data lists include Solo PVE: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Solo PVE?
The game's server browser reads these tags from Solo PVE: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Solo PVE?
Enter client.connect 107.136.237.168:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.