Station XX-6253 · no signal
ビビラス高難易度サーバー
Offline 31.58.47.54:29015 checked 1d ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 6
- Rank
- #6,253
- top 28%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −4into Tue 17:00 UTC
- Peak · 48 h
- 6most 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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 28% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 18 Oct, 15:46 UTC10d ago | M0.0■steady | 0 | – | 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 pageRules and settings
Which map is running on ビビラス高難易度サーバー?
The procedural map on ビビラス高難易度サーバー is size 4,000 with seed 1337, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.
Which settings and rules apply on ビビラス高難易度サーバー?
You will find no gather rate in the name of ビビラス高難易度サーバー. At the game's default, groups can have up to 8 players. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on ビビラス高難易度サーバー?
A reading taken now finds ビビラス高難易度サーバー offline; the most recent activity was 30 hours ago. The seven-day average is 0 players, with a peak of 6. Averaged over the last 48 hours, the busiest hour was 16:00 UTC at 4 players.
How does ビビラス高難易度サーバー rank against other Rust servers?
Over the last seven days, ビビラス高難易度サーバー recorded enough player hours to reach #6,253 worldwide, placing it in the top 28% of all ranked servers.
Operator and location
How reliably does ビビラス高難易度サーバー stay online?
As recorded now, ビビラス高難易度サーバー is not reachable, the last contact having been 30 hours ago. The uptime it reports puts its last restart about 6 hours ago. 62 of 168 hours in the last 7 full days were up time, 37% of the total. On 14 October 2026 it was recorded for the first time by Rust Server Trends.
Does ビビラス高難易度サーバー hold a steady tick rate?
Its average server fps over the last 48 hours was 228, and it never dropped below 219. At its highest, it carried 72,342 entities: buildings, deployables and the world's other contents. Its highest memory use was 2,828 MB. What you feel as lag is the combination of low fps and a rising entity count.
Which region does ビビラス高難易度サーバー run from?
The name of ビビラス高難易度サーバー points to Asia, even though it publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 31.58.47.54:29015.
What build of Rust does ビビラス高難易度サーバー use?
Rust network protocol 2635 and build 168909 on Linux is what ビビラス高難易度サーバー runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on ビビラス高難易度サーバー?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does ビビラス高難易度サーバー run its wipes?
The rhythm of ビビラス高難易度サーバー cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 10 days 7 hours is how long the current world has been running.
Tags
What do the server tags on ビビラス高難易度サーバー mean?
These are the tags ビビラス高難易度サーバー publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp500 (Max players): Slots: 500; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does ビビラス高難易度サーバー appear?
These Rust Server Trends lists include ビビラス高難易度サーバー: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto ビビラス高難易度サーバー?
To join, enter client.connect 31.58.47.54:29015 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.
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.