ビビラスサーバー
Offline 31.58.47.54:29115 checked 1d ago
Server instruments
last reading Tue 17:00 UTCPlayers now
7% full 7-day avg7-day peakServer fps
48 h low 83 · below 20 is lag, below 10 is badEntities
48 h range 76,862–86,452 · memory 3,065 MBUptime
6 h 15 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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 5% 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.
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 15:46 UTC10d ago | 0 | – | 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- 29/100
- 23/200
- 2/100
- 6/100
- 21/100
- 19/100
Quick answers
from the figures on this pageWipe timing
What happens on ビビラスサーバー when wipe day comes?
The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.
What wipe timing does ビビラスサーバー follow?
Its rhythm cannot be told from the wipes of ビビラスサーバー on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 10 days 12 hours ago the current world was made.
Tag meanings
Which tags does ビビラスサーバー carry, and what do they mean?
Tags published by ビビラスサーバー, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does ビビラスサーバー appear in Rust Metrics lists and filters?
On Rust Metrics, ビビラスサーバー sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Players now: At least 10; Average players: 10+ on average.
Population
Where does ビビラスサーバー sit in the rankings?
Ranking for ビビラスサーバー: #1,088 on seven-day player hours, top 5% of all ranked servers.
What player count does ビビラスサーバー carry?
Status for ビビラスサーバー: offline. Last seen 35 hours ago. Seven-day check: 21 players on average. Peak reading: 49. Check: 48-hour peak. 15:00 UTC, 40 players on average.
Server details
Which location does ビビラスサーバー run from?
The name of ビビラスサーバー points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 31.58.47.54:29115.
What Rust version is ビビラスサーバー on?
Rust network protocol 2635 and build 168909 on Linux is the build ビビラスサーバー runs. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on ビビラスサーバー within range?
Over the last 48 hours the average was 103 server fps; the floor was 83. Peak entity count: 86,452. Buildings, deployables and all else included. Memory peak: 3,065 MB. Expect lag when fps falls and entities climb.
What is the uptime on ビビラスサーバー, and is it online?
Check: connection. ビビラスサーバー is offline at this moment. Last contact was 35 hours ago. Reading: uptime. About 6 hours ago it restarted, on its own count. Reading: 37% uptime over the last 7 full days. It was up 62 of 168 hours. Check: first contact. Rust Metrics logged it on 14 October 2026.
Map and rules
What settings and rules apply on ビビラスサーバー?
No gather rate appears in the name: ビビラスサーバー. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on ビビラスサーバー?
Check: map. Procedural, size 3,900, seed 1337, generated by the game on ビビラスサーバー. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Custom Map.
Connection
What do you do to join ビビラスサーバー?
Check: join. Open Rust, press F1, then enter client.connect 31.58.47.54:29115. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.