Online 78.29.13.139:28015 checked 8m ago
Vanilla PvE, but...
Connect
srv = rust.server("78.29.13.139:28016")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 21 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 bestTop 13% 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 29 October, 16:45 UTC, in 10h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 10h | Thu 29 Oct, 16:45 UTC | wipe |
| 1 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 14d 10h | Thu 12 Nov, 16:45 UTC | wipe |
| 3 | 28d 10h | Thu 26 Nov, 16:45 UTC | wipe |
| 4 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 42d 10h | Thu 10 Dec, 16:45 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 11, 47 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 16:45 UTC13d ago | 11 | NaN | running | 0 |
| 1 | Thu 1 Oct, 17:48 UTC FW27d ago | 9+1 queue | halved by day 4 | 14 days | 0 |
| 2 | Mon 21 Sep, 17:51 UTC37d ago | 10 | halved by day 3 | 10 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
4500 · seed 27051999
- map
- Procedural Map
- size
- 4500
- seed
- 27051999
Server
srv.info()- address
- 78.29.13.139:28015
- region
- –
- max players
- 13
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 16:45 UTC
- hostname
- ^
- first seen
- 21 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 · 252 on average | 188/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 241 on average | 87/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 105 on average | 59/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 56/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 50 on average | 20/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 48 on average | 24/250 |
Quick answers
From the figures on this page.
Player counts
How does Vanilla PvE, but... compare in the rankings?
Player hours over seven days put Vanilla PvE, but... at #3,000, in the top 13% of the ranked set.
How many players does Vanilla PvE, but... hold at once?
Current row: 0 players on Vanilla PvE, but..., against 13 slots. Over the last seven days it averaged 1 players and peaked at 7. The 48-hour sample puts the busiest hour at 16:00 UTC, averaging 5 players.
About the server
How well does Vanilla PvE, but... perform?
Server fps over the last 48 hours averages 118; the floor is 79. The entity count peaked at 137,863, covering buildings, deployables and the rest of the world. The memory field tops out at 4,196 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Vanilla PvE, but... on?
Rust network protocol 2635 and build 168909 on Windows is what Vanilla PvE, but... runs. The protocol has to match before you can join, and Steam does the updating.
Is Vanilla PvE, but... up, and what does its uptime show?
Online is the state at the latest refresh for Vanilla PvE, but.... The uptime it reports puts the last restart about 2 hours ago. 162 of 168 hours up over the last 7 full days, or 96%. Rust Data logged it first on 21 September 2026.
In which location is Vanilla PvE, but... hosted?
There is no region published for Vanilla PvE, but.... The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 78.29.13.139:28015.
Map and rules
What rules and settings are recorded for Vanilla PvE, but...?
No gather rate appears in the name: Vanilla PvE, but.... Eight players per group: that is the game's default, and it applies here. pve is the game mode here, and player combat is not allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Vanilla PvE, but... loaded?
Size 4,500, seed 27051999: the procedural map on Vanilla PvE, but..., generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does Vanilla PvE, but... wipe, and how often?
The tag sets the prediction: Vanilla PvE, but... has too few wipes on record to confirm its schedule. On Thursday 29 October at 16:45 UTC the next wipe is due. A new world was started 13 days 13 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
On Vanilla PvE, but..., what happens on wipe day?
Across recent wipes the busiest point averaged 10 players. The crowd on the latest wipe topped out 47 hours after it began. 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 3.5.
Lists and tags
Where does Vanilla PvE, but... appear among Rust Data lists and filters?
These Rust Data lists include Vanilla PvE, but...: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: 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 2 weeks.
How should you read the server tags on Vanilla PvE, but...?
Read by the game's server browser, the tags Vanilla PvE, but... publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp13 (Max players): Slot count: 13; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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 to join Vanilla PvE, but...?
The manual route: launch Rust, F1, then client.connect 78.29.13.139:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/khgSbbBgEW is the website recorded for it.