RUST METRICSFlight deck · live data
Data live Servers11,640 Players39,046 Populated2,948 Fresh wipes 3 h72 Scan5 min
‹ All servers162.43.36.237:29015
Online Full Queue Fresh wipe Wipe due No query

ビビラスデバッグサーバー

Online 162.43.36.237:29015 checked 8m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 01: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 103 SERVER FPS

Server fps

48 h low 56 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 82,504 ×1000

Entities

48 h range 64,814–83,002 · memory 2,480 MB
1239 ET SINCE RESTART 06:05

Uptime

6 h 5 min since its last restart, at the last reading
7-day average0peak 6
Rank#5,118top 23%
Last wipe26d agono schedule published
Next wipe8d 15hThu 5 Nov, 19:00 UTC FW
Memory2,480MB48 h peak 6 players
REC 1

Players

AveragePeak
0246804:0013:0022:0007:0016:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020004:0013:0022:0007:0016:0001: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence

wipe-day peak3players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 15hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 15hFW

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 22:11 UTC FW26d ago 3 – 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

Wipe timing

What should you expect from wipe day on ビビラスデバッグサーバー?

At their busiest, its recent wipes drew 3 players on average. 17 hours after the wipe, the crowd peaked on the latest wipe.

How often does ビビラスデバッグサーバー wipe, and when?

Once a month ビビラスデバッグサーバー wipes, with the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 26 days 4 hours ago.

Tags

Which tags does ビビラスデバッグサーバー carry, and what do they mean?

These are the tags ビビラスデバッグサーバー publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. 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. 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.

Population

What position does ビビラスデバッグサーバー hold among Rust servers?

Ranking for ビビラスデバッグサーバー: #5,118 on seven-day player hours, top 23% of all ranked servers.

How full does ビビラスデバッグサーバー get?

Current headcount on ビビラスデバッグサーバー: 0 players, 500 slots available. Seven-day check: 0 players on average. Peak reading: 6. Check: 48-hour peak. 05:00 UTC, 3 players on average.

Server details

Where does ビビラスデバッグサーバー sit?

Reading: location. Nothing in the tags, but the name of ビビラスデバッグサーバー points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 162.43.36.237:29015.

What Rust version is ビビラスデバッグサーバー on?

Reading: ビビラスデバッグサーバー, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on ビビラスデバッグサーバー within range?

Check: fps. Average 95 server fps over the last 48 hours, low of 56. Within range. Check: entities. The peak was 83,002, counting buildings, deployables and the rest of the world. Reading: 3,223 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

Is ビビラスデバッグサーバー up, and how often does it stay up?

Reading: online. ビビラスデバッグサーバー answers right now. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is ビビラスデバッグサーバー configured, and what rules are in force?

Check: gather rate. The name ビビラスデバッグサーバー does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on ビビラスデバッグサーバー?

Size 3,900 and seed 1337: the game generates the procedural map on ビビラスデバッグサーバー from them. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Connection

What do you do to join ビビラスデバッグサーバー?

To join: start Rust, press F1 and type client.connect 162.43.36.237:29015. Or press Launch Rust here and Steam opens the game and connects you.

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 Slots: 500.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.