VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP
Online EA 118.104.165.193:28015 checked 12m ago
Server instruments
last reading Thu 18:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 62 · below 20 is lag, below 10 is badEntities
48 h range 206,094–216,885 · memory 7,124 MBUptime
22 h 59 min since its last restart, at the last readingPlayers
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
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 23hFW
- WPT 2Thu 3 Dec, 19:00 UTC34d 23hFW
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 19:10 UTC FW28d ago | 41 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 25/100
- 17/88
- 13/100
- 7/100
- 3/200
- 7/100
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
At their busiest, its recent wipes drew 41 players on average. Peak crowd on the latest wipe: 44 hours in.
How often does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP wipe, and when?
Once a month VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 27 days 19 hours ago. Its tags carry a monthly wipe schedule.
Tags
How should you read the tags on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server; EA (East Asia): The server browser files it under East Asia from VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
Rust Metrics lists featuring VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: 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.
Player count
Where does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP sit in the rankings?
Player hours over the last seven days put VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP at #1,662, #164 in Asia, in the top 7% of all ranked servers.
What player count does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP carry?
0 of 50 slots are filled on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP right now. Seven-day check: 3 players on average. Peak reading: 11. The last 48 hours peaked at 13:00 UTC, averaging 8 players at that hour.
Operator and location
What location is VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP hosted in?
Its EA tag places VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP in Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 118.104.165.193:28015.
What Rust version is VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP on?
Rust network protocol 2635 and build 168909 on Linux is the build VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP runs. To get in, your game needs the same protocol; Steam applies the update.
Is performance on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP within range?
Check: fps. Average 89 server fps over the last 48 hours, low of 62. Within range. Peak entity count: 216,885. Buildings, deployables and all else included. Check: memory. Peak use was 7,212 MB. Expect lag when fps falls and entities climb.
What is the uptime on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP, and is it online?
VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 22 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP enforce, and what are its settings?
No gather rate appears in the name: VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP. No limit is set beyond the default. Groups take up to 8 players. pve, other players are not fought — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.
What map is VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP on?
From seed 597347015, the game generates the procedural map on VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP. Its size is 4,500. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
How can you get onto VIVIDUS PvE|Loads of Battle Content|Stress-Free Settings|EN/JP?
Check: join. Open Rust, press F1, then enter client.connect 118.104.165.193:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://www.vividus.online/ is where its website sits.