[JP][PVE] BalloonBear [gahu3]
126.77.90.98:28020 checked 10m ago
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 25% 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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 18:32 UTC1d ago | – | – | 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.
Similar servers
Quick answers
Rules and settings
What settings does [JP][PVE] BalloonBear [gahu3] run?
No gather rate appears in the name [JP][PVE] BalloonBear [gahu3]. Up to 8 players can group, which is the game's default. It runs pve, other players cannot be fought. This one sits under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running on it. VAC, Valve's anti-cheat, is switched on.
What is the map on [JP][PVE] BalloonBear [gahu3]?
The game generates the procedural map of size 3,000 on [JP][PVE] BalloonBear [gahu3] with seed 436589391. You can view it on RustMaps from this page, since the same size and seed give the same map.
Population
How full is [JP][PVE] BalloonBear [gahu3]?
The server [JP][PVE] BalloonBear [gahu3] is currently at 2 players out of 30 slots. The seven-day average is 1 players, with a peak of 4. The highest average over the last 48 hours came at 12:00 UTC, with 4 players.
What is [JP][PVE] BalloonBear [gahu3]'s ranking?
In the top 25% of ranked servers, [JP][PVE] BalloonBear [gahu3] holds #5,565 for player hours over the last seven days.
Tags and filters
What do [JP][PVE] BalloonBear [gahu3]'s tags indicate?
The game's server browser reads these tags from [JP][PVE] BalloonBear [gahu3]: gmrust (Game mode): Standard survival gameplay; mp30 (Max players): Capacity: 30; ts8 (Group limit): The team cap is 8, which is the game's default; v2634 (Protocol): To join, your game must match protocol 2634; cs167584 (Build): The game build is 167584; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the environment is the threat; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The Modded listing means plugins or settings have changed the game. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.
Which Rust Zerg Life filters and lists cover [JP][PVE] BalloonBear [gahu3]?
Modded Rust servers for clans and zergs and Best Rust PvE servers: that is where you will find [JP][PVE] BalloonBear [gahu3] among the Rust Zerg Life rankings. Under these filters it shows on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Server details
Is [JP][PVE] BalloonBear [gahu3] currently online and stable?
You can join [JP][PVE] BalloonBear [gahu3] now: it is online. The uptime figure it gives suggests it restarted around 4 hours ago. It was up 18% of the time across the last 7 full days: 30 of 168 hours. The first time Rust Zerg Life saw it was on 13 September 2026.
What is the performance like on [JP][PVE] BalloonBear [gahu3]?
Server fps held an average of 207 for the last 48 hours, with a minimum of 169. It reached a maximum of 46,151 entities, covering buildings, deployables and the rest of the world. Memory use peaked at 2,022 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.
Which Rust build does [JP][PVE] BalloonBear [gahu3] use?
Rust network protocol 2634 and build 167584 is what [JP][PVE] BalloonBear [gahu3] runs, on Windows. Joining requires your game to be on the same protocol, which Steam updates automatically.
What is the location of [JP][PVE] BalloonBear [gahu3]?
Its name points to Asia, though [JP][PVE] BalloonBear [gahu3] publishes no region tag. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 126.77.90.98:28020.
Wipe cycle
When does [JP][PVE] BalloonBear [gahu3] wipe?
With so few wipes on record for [JP][PVE] BalloonBear [gahu3], its pattern is not yet clear. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. 37 hours ago is when its present world was created.
Connect
How can I connect to [JP][PVE] BalloonBear [gahu3]?
Enter client.connect 126.77.90.98:28020 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp30,ptrak,$r?,v2634,^p,gmrust,cs167584,ts8,^o^z
Game
gmrust
mp30
ts8
v2634
cs167584
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
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.