RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers31.58.47.54:29015
Offline Full Queue Fresh wipe Wipe due No query

ビビラス高難易度サーバー

Offline 31.58.47.54:29015 checked 1d ago

moddedoxide
COM 1 · connect

Server instruments

last reading Tue 17:00 UTC
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 225 SERVER FPS

Server fps

48 h low 219 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 71,987 ×1000

Entities

48 h range 67,081–72,342 · memory 2,828 MB
1239 ET SINCE RESTART 06:16

Uptime

6 h 16 min since its last restart, at the last reading
7-day average0peak 6
Rank#6,259top 28%
Last wipe10d agono schedule published
Next wipe–too few wipes seen yet
Memory2,828MB48 h peak 6 players
REC 1

Players

AveragePeak
0246809:0011:0012:0014:0015:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040009:0011:0012:0014:0015:0017:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct22 Oct25 Oct28 Oct

Top 28% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on ビビラス高難易度サーバー?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does ビビラス高難易度サーバー follow?

The rhythm of ビビラス高難易度サーバー's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 10 days 4 hours ago the current world was made.

Tags

How should you read the tags on ビビラス高難易度サーバー?

These are the tags ビビラス高難易度サーバー publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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.

Player count

Where does ビビラス高難易度サーバー sit in the rankings?

Player hours over seven days put ビビラス高難易度サーバー at #6,259, in the top 28% of all ranked servers.

How full does ビビラス高難易度サーバー get?

Reading for ビビラス高難易度サーバー: offline at this moment; last seen 27 hours ago. Check: players over seven days. Average 0, peak 6. Average at the busiest hour was 4 players, at 16:00 UTC over the last 48 hours.

Server

Where does ビビラス高難易度サーバー sit?

Reading: location. Nothing in the tags, but the name of ビビラス高難易度サーバー points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 31.58.47.54:29015.

What Rust version is ビビラス高難易度サーバー on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by ビビラス高難易度サーバー. Matching protocol is required to join. Let Steam update your game.

How does ビビラス高難易度サーバー perform?

Over the last 48 hours the average was 228 server fps; the floor was 219. Check: entities. The peak was 72,342, counting buildings, deployables and the rest of the world. Reading: 2,828 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is ビビラス高難易度サーバー, and is it online now?

Check: connection. ビビラス高難易度サーバー is offline at this moment. Last contact was 27 hours ago. By its reported uptime, the last restart was roughly 6 hours ago. Reading: 37% uptime over the last 7 full days. It was up 62 of 168 hours. The first sighting on Rust Metrics was 14 October 2026.

Map and rules

What rules does ビビラス高難易度サーバー enforce, and what are its settings?

No gather rate appears in the name: ビビラス高難易度サーバー. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on ビビラス高難易度サーバー?

Check: map. Procedural, size 4,000, seed 1337, generated by the game on ビビラス高難易度サーバー. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.

How to join

How can you get onto ビビラス高難易度サーバー?

Press F1 in Rust and enter client.connect 31.58.47.54:29015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.