Station XX-5115 · recording
ビビラスデバッグサーバー
Online 162.43.36.237:29015 checked 1h ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 6
- Rank
- #5,115
- top 23%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 8d 0h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +3into Wed 16:00 UTC
- Peak · 48 h
- 4most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 23% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 0h. The force wipe · high confidence
- wipe-day peak
- 3players, last three wipes
Coming wipes
- 8d 0hThu 5 Nov, 19:00 UTCFW
- 36d 0hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 22:11 UTC FW26d ago | M0.5▲rising | 3 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on ビビラスデバッグサーバー?
The procedural map on ビビラスデバッグサーバー is size 3,900 with seed 1337, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.
Which settings and rules apply on ビビラスデバッグサーバー?
The name of ビビラスデバッグサーバー gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on ビビラスデバッグサーバー right now?
A reading taken now shows 0 players on ビビラスデバッグサーバー, which has 500 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 6. The busiest point in the last 48 hours came at 16:00 UTC, averaging 3 players.
How does ビビラスデバッグサーバー rank against other Rust servers?
Over the last seven days, ビビラスデバッグサーバー recorded enough player hours to reach #5,115 worldwide, placing it in the top 23% of all ranked servers.
Server details
How reliably does ビビラスデバッグサーバー stay online?
Right now, you can reach ビビラスデバッグサーバー. Its reported uptime points to a restart about 21 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Does ビビラスデバッグサーバー hold a steady tick rate?
Across the last 48 hours it averaged 96 server fps, with a floor of 56. Buildings, deployables and all the rest of the world's entities brought it to a high of 83,002. Memory use peaked at 3,223 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does ビビラスデバッグサーバー run from?
No region tag comes from ビビラスデバッグサーバー, though the name points to Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 162.43.36.237:29015.
Which Rust version is ビビラスデバッグサーバー running?
ビビラスデバッグサーバー is running Rust network protocol 2635 and build 168909 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on ビビラスデバッグサーバー?
On average, the busiest point of its recent wipes drew 3 players. The peak on the most recent wipe came 17 hours after the wipe.
On what timetable does ビビラスデバッグサーバー run its wipes?
At the force wipe each month ビビラスデバッグサーバー wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 26 days 20 hours.
Server tags
What do the server tags on ビビラスデバッグサーバー mean?
These are the tags ビビラスデバッグサーバー publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does ビビラスデバッグサーバー appear?
You will find ビビラスデバッグサーバー on the following Rust Server Trends lists: Modded Rust servers, tracked 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.
How to join
What steps get you onto ビビラスデバッグサーバー?
Enter client.connect 162.43.36.237:29015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.