Statistical profileOffline
ビビラスサーバー
31.58.47.54:29115 checked 1d ago
Connect to this server
1. Main points
Players now
35/ 500
7% full
7-day average
21
peak 49
Rank
#1,089
top 5%
Last wipe
10d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 35 players on it, 7% of its 500 slots.
- Over the last seven days it averaged 21 players, with a peak of 49.
- It ranks #1,089 of all ranked servers, the top 5%, on player hours over the last seven days.
- Its current map went up 10d ago.
2. Players
Figure 1: Players on ビビラスサーバー
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 5% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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 peak
0
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 18 Oct, 15:46 UTC10d ago | 0 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
8. Server characteristics
Table 3: Characteristics of ビビラスサーバー
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 24 on average | 29 / 100 |
| 【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 | EA · groups of 8+ · weekly · 20 on average | 23 / 200 |
| [JP]初心者PVPサーバー|RaidTime・ Events | EA · groups of 10+ · biweekly · 16 on average | 6 / 100 |
| [守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新 | EA · no group limit · 11 on average | 21 / 100 |
| [JP] DON-tacos PvE | EA · groups of 8+ · monthly · 11 on average | 8 / 100 |
| #10-[搞就完了]10倍/10.29新档/无权/萌新首选 | EA · no group limit · 11 on average | 18 / 100 |
10. Quick answers
From the figures on this page.
Wipe details
On what schedule are wipes carried out on ビビラスサーバー?
The rhythm of ビビラスサーバー's wipes cannot yet be told: too few are on record. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. This world was generated 10 days 15 hours ago.
On ビビラスサーバー, what happens on wipe day?
Recent wipes drew an average peak of 0 players. The peak of the latest wipe's crowd came 0 hours after it began.
About the server
How reliable is ビビラスサーバー, and is it online now?
ビビラスサーバー is offline at the time of this release; it was last seen 38 hours ago. About 6 hours ago is when it last restarted, according to the uptime it reports. 62 of 168 hours on across the last 7 full days gives an uptime of 37%. The first sighting of it by Rust Census was on 14 October 2026.
What does the performance record of ビビラスサーバー show?
Average server fps over the last 48 hours was 103, with a low of 83. Buildings, deployables and everything else in the world took the entity count to 86,452. The peak memory use recorded was 3,065 MB. What players experience as lag is low fps combined with a climbing entity count.
In which location is ビビラスサーバー based?
Pointing to Asia is ビビラスサーバー's name, though no region tag is published. Rust Census does not look up where the machine stands; it shows where a server says it is. 31.58.47.54:29115 is its address.
On which Rust version does ビビラスサーバー operate?
This release lists ビビラスサーバー on Rust network protocol 2635 and build 168909, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
How many players does ビビラスサーバー carry?
The last count for ビビラスサーバー was 38 hours ago; it is offline at present. Averaged over seven days: 21 players, with a peak of 49. The busiest hour in the last 48 hours was 15:00 UTC, with an average of 40 players.
What position does ビビラスサーバー hold in the server rankings?
For seven-day player hours, ビビラスサーバー is ranked #1,089, placing it in the top 5% of all ranked servers.
Tags, lists
Where does ビビラスサーバー appear among the Rust Census lists and filters?
The Rust Census lists that ビビラスサーバー fits are: Modded Rust servers, counted. 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; Last wipe: In the last 2 weeks; Players now: At least 10; Average players: 10+ on average.
Which meanings do the tags on ビビラスサーバー carry?
gmrust (Game mode): Survival play, in the standard Rust format; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): Game build: 168909; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): This server is listed as modded, with plugins or settings that change the game are the tags ビビラスサーバー publishes, and the game's server browser reads them. At the top of this page you will find the tags for current players, queue and world creation time.
Rules, map
Which map is in use on ビビラスサーバー?
Size 3,900 and seed 1337: that is the procedural map on ビビラスサーバー, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page. Recorded under map name: Custom Map.
On ビビラスサーバー, what rules and settings are in force?
No gather rate is recorded for ビビラスサーバー in its name. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. Modded is its section in the server browser, because plugins or settings change the game. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
Join details
What steps are needed to join ビビラスサーバー?
You can open the console in Rust with F1 and enter client.connect 31.58.47.54:29115; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp500 | Max players The server holds 500 slots. |
ts8 | Group limit This is the game default: 8 to a team. |
v2635 | Protocol Protocol 2635 is required; a different version cannot join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded This server is listed as modded, with plugins or settings that change the 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.