Station EA-1662 · recording
VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP
Online EA 118.104.165.193:28015 checked 13m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 3
- peak 11
- Rank
- #1,662
- top 7% · #164 in EA
- Last wipe
- 27d ago
- monthly schedule
- Next wipe
- 6d 23h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −3into Thu 14:00 UTC
- Peak · 48 h
- 9most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 7% of all ranked servers, top 31% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 23h. The force wipe · high confidence
- wipe-day peak
- 41players, last three wipes
Coming wipes
- 6d 23hThu 5 Nov, 19:00 UTCFW
- 34d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 41, 44 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 19:10 UTC FW28d ago | M1.6▲rising | 41 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP runs a procedural map of size 4,500 with seed 597347015, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
The name of VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP gives no gather rate. At the game's default, groups can have up to 8 players. In pve mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
A reading taken now shows 0 players on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP, which has 50 slots. Across seven days this server recorded an average of 3 players and a peak of 11. The last 48 hours show their highest activity at 13:00 UTC, averaging 8 players.
How does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP rank against other Rust servers?
VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP is #164 in Asia and #1,662 worldwide on the past week's player hours, within the top 7% of ranked servers.
Operator and location
How reliably does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP stay online?
VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP is up at the moment. The uptime it reports puts its last restart about 22 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP perform under load?
Across the last 48 hours it averaged 89 server fps, with a floor of 62. The world held up to 216,885 entities at its peak, buildings and deployables included. It reached a ceiling of 7,212 MB of memory. Low fps together with a growing entity count is what players experience as lag.
Where in the world is VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP hosted?
The EA tag is how VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 118.104.165.193:28015.
What build of Rust does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP use?
Rust network protocol 2635 and build 168909 on Linux is what VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
The recent wipes averaged a busiest count of 41 players. 44 hours into the latest wipe, the crowd reached its peak.
On what timetable does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP run its wipes?
Once a month VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP wipes, at the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 27 days 19 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Server tags
What do the server tags on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP mean?
Tags published by VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP appear?
You will find VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How to join
What steps get you onto VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
To join, enter client.connect 118.104.165.193:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://www.vividus.online/.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.