Rust Data

rustdata.spaceservers162.43.36.237:29016.ipynb

Run all rust-data · live

‹ All servers

Online 162.43.36.237:29015 checked 8m ago

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

moddedoxide

Connect

srv = rust.server("162.43.36.237:29016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/500 # 0% full
7-day average 0 # peak 6
rank #5,109 # top 23%
last wipe 26d ago # no schedule published
next wipe 7d 20h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020023:0008:0017:0001:0010:0020: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. # The force wipe · high confidence

wipe-day peak3players, last three wipes

Coming wipes

inatkind
07d 20hThu 5 Nov, 19:00 UTCFW force wipe
135d 20hThu 3 Dec, 19:00 UTCFW force wipe

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 22:11 UTC FW26d ago 3 NaN 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.

display(srv.map, srv.info())

Map

3900 · seed 1337
Map of ビビラスデバッグサーバー
map
Custom Map
size
3900
seed
1337

Server

srv.info()
address
162.43.36.237:29015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 22:11 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 24 on average29/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 19 on average31/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average1/100
3[JP] DON-tacos PvEEA · groups of 8+ · monthly · 11 on average2/100
4#10-[搞就完了]10倍/10.28新档/无权/萌新首选EA · no group limit · 11 on average18/100
5[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 11 on average20/100

Quick answers

From the figures on this page.

Population

How does ビビラスデバッグサーバー compare in the rankings?

Over the last seven days ビビラスデバッグサーバー sits at #5,109 on player hours, in the top 23% of ranked servers.

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

ビビラスデバッグサーバー reports 0 players at this refresh, with 500 slots configured. Over the last seven days it averaged 0 players and peaked at 6. Averaged by hour over 48 hours, 16:00 UTC is the busiest, at 3 players.

Server facts

How well does ビビラスデバッグサーバー perform?

Averaged over 48 hours: 96 server fps, never under 56. The entity count peaked at 83,002, covering buildings, deployables and the rest of the world. The memory field tops out at 3,223 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does ビビラスデバッグサーバー run?

Rust network protocol 2635 and build 168909 on Linux is what ビビラスデバッグサーバー runs. Joining needs the same protocol on your game; Steam handles the update.

Is ビビラスデバッグサーバー up, and what does its uptime show?

The current sample puts ビビラスデバッグサーバー online. A restart about 58 minutes ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.

In which location is ビビラスデバッグサーバー hosted?

No region tag is published by ビビラスデバッグサーバー, though its name points to Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 162.43.36.237:29015.

Map and rules

Which settings and rules does ビビラスデバッグサーバー run?

No gather rate appears in the name: ビビラスデバッグサーバー. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has ビビラスデバッグサーバー loaded?

Size 3,900, seed 1337: the procedural map on ビビラスデバッグサーバー, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.

Wipes and dates

When does ビビラスデバッグサーバー wipe, and on what schedule?

Once a month ビビラスデバッグサーバー wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 26 days 23 hours ago, and that is the one in play.

What is wipe day on ビビラスデバッグサーバー like?

The average peak over recent wipes is 3 players. Peak population on the latest wipe came 17 hours in.

Lists and tags

Where does ビビラスデバッグサーバー appear among Rust Data lists and filters?

The Rust Data lists that ビビラスデバッグサーバー fits are: Modded Rust servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on ビビラスデバッグサーバー hold?

These tags are published by ビビラスデバッグサーバー and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into ビビラスデバッグサーバー?

The manual route: launch Rust, F1, then client.connect 162.43.36.237:29015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp500
Max players 500 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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.

Rust Data 65,961 players 11,791 servers online