Rust Data

rustdata.spaceservers31.58.47.54:29116.ipynb

Run all rust-data · live

‹ All servers

Offline 31.58.47.54:29115 checked 1d ago

ビビラスサーバー

moddedoxide

Connect

srv = rust.server("31.58.47.54:29116")
print(srv.connect_command)

Right now

srv.summary()
players now 35/500 # 7% full
7-day average 21 # peak 49
rank #1,090 # top 5%
last wipe 10d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
02040608009:0011:0012:0014:0015:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020009: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 18 Oct, 15:46 UTC10d ago 0 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
31.58.47.54:29115
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 15:46 UTC
hostname
–
first seen
14 Oct 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 average32/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 19 on average23/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 average6/100
4[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 11 on average20/100
5#10-[搞就完了]10倍/10.29新档/无权/萌新首选EA · no group limit · 11 on average17/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does ビビラスサーバー rank?

Over the last seven days ビビラスサーバー sits at #1,090 on player hours, in the top 5% of ranked servers.

How many players does ビビラスサーバー hold at once?

ビビラスサーバー returns no live count at this refresh, having last been seen 34 hours ago. Over the last seven days it averaged 21 players and peaked at 49. Averaged by hour over 48 hours, 15:00 UTC is the busiest, at 40 players.

Server data

How well does ビビラスサーバー perform?

The 48-hour average is 103 server fps, with a low of 83. The entity count peaked at 86,452, covering buildings, deployables and the rest of the world. A high of 3,065 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is ビビラスサーバー on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by ビビラスサーバー. The protocol has to match before you can join, and Steam does the updating.

How reliable is ビビラスサーバー, and is it online now?

Offline now for ビビラスサーバー, last seen 34 hours ago. Count back 6 hours from its reported uptime to get the last restart. 62 of 168 hours up over the last 7 full days, or 37%. Its earliest recorded date in Rust Data is 14 October 2026.

Where does ビビラスサーバー sit?

Its name points to Asia, but ビビラスサーバー publishes no region tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 31.58.47.54:29115.

Rules, settings, map

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

No gather rate appears in the name: ビビラスサーバー. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.

What is the map on ビビラスサーバー?

ビビラスサーバー runs a procedural map of size 3,900 with seed 1337, 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.

Wipe data

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

Too few wipes are on record for ビビラスサーバー to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 11 hours ago.

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

Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.

Tags and filters

Which lists on Rust Data hold ビビラスサーバー, and which filters?

These Rust Data lists include ビビラスサーバー: Modded Rust servers. 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; Players now: At least 10; Average players: 10+ on average.

How should you read the server tags on ビビラスサーバー?

Read by the game's server browser, the tags ビビラスサーバー publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): Slot count: 500; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to ビビラスサーバー?

Enter client.connect 31.58.47.54:29115 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp500
Max players Slot count: 500.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 34,939 players 11,686 servers online