Station XX-4097 · recording
[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 8m ago
- Players now
- 0/ 30
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 6
- Rank
- #4,097
- top 18%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 30 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +0into Mon 14:00 UTC
- Peak · 48 h
- 1most 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 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 6players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 40 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 12 Oct, 18:32 UTC15d ago | M0.8▲rising | 6 | – | 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 pageServer rules
Which map is running on [JP][PVE] BalloonBear [gahu3]?
Generated by the game, the map on [JP][PVE] BalloonBear [gahu3] is procedural, size 3,000 with seed 436589391. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [JP][PVE] BalloonBear [gahu3]?
No gather rate appears in the name of [JP][PVE] BalloonBear [gahu3]. The group limit is 8 players, the game's default. pve is the game mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on [JP][PVE] BalloonBear [gahu3] right now?
0 of the 30 slots on [JP][PVE] BalloonBear [gahu3] are filled right now. The seven-day average is 0 players, with a peak of 6. The last 48 hours show their highest activity at 13:00 UTC, averaging 0 players.
How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?
The last seven days of player hours place [JP][PVE] BalloonBear [gahu3] at #4,097, in the top 18% of all ranked servers.
Server details
How reliably does [JP][PVE] BalloonBear [gahu3] stay online?
As recorded now, [JP][PVE] BalloonBear [gahu3] is running. The uptime it reports puts its last restart about 2 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does [JP][PVE] BalloonBear [gahu3] hold a steady tick rate?
Its average server fps over the last 48 hours was 200, and it never dropped below 105. The world held up to 50,681 entities at its peak, buildings and deployables included. It reached a ceiling of 2,373 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does [JP][PVE] BalloonBear [gahu3] run from?
Its name points to Asia, but [JP][PVE] BalloonBear [gahu3] publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 126.77.90.98:28020.
What build of Rust does [JP][PVE] BalloonBear [gahu3] use?
[JP][PVE] BalloonBear [gahu3] is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on [JP][PVE] BalloonBear [gahu3]?
The recent wipes averaged a busiest count of 6 players. The peak on the most recent wipe came 40 hours after the wipe.
How often does [JP][PVE] BalloonBear [gahu3] wipe, and on which days?
Too few wipes of [JP][PVE] BalloonBear [gahu3] are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 15 days 17 hours.
Lists and tags
What do the server tags on [JP][PVE] BalloonBear [gahu3] mean?
These are the tags [JP][PVE] BalloonBear [gahu3] publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp30 (Max players): Slots: 30; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does [JP][PVE] BalloonBear [gahu3] appear?
You will find [JP][PVE] BalloonBear [gahu3] on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto [JP][PVE] BalloonBear [gahu3]?
Enter client.connect 126.77.90.98:28020 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.