[JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】
Online 118.27.228.193:28015 checked 8m ago
Measurements
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
Top 5% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. 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 19, 6 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 23:58 UTC6d ago | 19 | – | running | 0 |
| Thu 1 Oct, 22:04 UTC FW27d ago | 23 | halved by day 9 | 21.1 days | 3 |
| Thu 17 Sep, 22:19 UTC41d ago | 13 | held half | 14 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.
Quick answers
Player counts
How does [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 rank against other Rust servers?
The last seven days of player hours place [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 at #1,031, within the top 5% of all ranked servers.
How busy is [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
Of its 100 slots, [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 is using 9 right now. We counted an average of 9 players in the past week, with 39 at the busiest. Look at the last 48 hours and 13:00 UTC stands out: it averaged 14 players.
Lists and tags
What do the server tags on [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 mean?
The game's server browser reads the tags [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 publishes: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^p (PvE): The danger is the world, not other players: players do not fight each other; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
These Rust Population lists include [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】: Modded Rust servers, counted and PvE servers, counted. Look for it under these filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Wipe notes
What does wipe day look like on [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
The busiest point of its recent wipes averaged 18 players. Peak came 6 hours into the latest wipe. In 50% of recent wipes, half the peak was held until the next wipe. In those that did not hold, the fall below half came by day 9.
What is the wipe schedule on [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
There is no next wipe to predict: [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 6 days 12 hours ago.
Settings
Which map does [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 run?
A procedural map of size 3,500 from seed 1711208204, generated by the game, is in use on [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】. The map follows from its size and seed, and RustMaps shows it from this page.
What are the rules and settings on [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
No gather rate appears in the name of [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】. Eight players per group is the default, and it applies here. pve is what it runs, no player combat. The server browser files it under Modded, where plugins or settings alter the game. Oxide plugins are in use here. You play with Valve's anti-cheat on: VAC.
Server details
Which version of Rust does [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 run?
On Linux, [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 runs Rust network protocol 2635 and build 168909. Your game needs the same protocol to join; Steam takes care of updating it.
Does [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 run smoothly?
In the last 48 hours, it averaged 55 server fps, with a low of 39. Entities peaked at 124,314, including buildings, deployables and everything else. Up to 4,158 MB of memory was used. Players feel lag when fps is low and the entity count climbs.
Is [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 online, and how reliable is it?
You will find [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 online now. About 5 hours ago, it restarted, according to its uptime. Over the last 7 full days, 165 of 168 hours were online, or 98%. On 13 September 2026, Rust Population saw it for the first time.
Where is [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】 located?
No region tag comes from [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】, but the name points to Asia. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. 118.27.228.193:28015 is where it lives.
Getting in
How do I join [JP]仮想空間-Virtual Space-【PvE|Event|Purge|Skill】?
To connect directly, open Rust's console with F1 and type client.connect 118.27.228.193:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. For more, visit its website: https://discord.com/invite/3zmC5unVD2.