[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 1h ago
Vital stats
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
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 18:32 UTC16d ago | 6 | – | 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include [JP][PVE] BalloonBear [gahu3]?
These Rust Pop Watch lists include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers, live and Rust PvE servers, ranked by who's hot. These are the filters that list it 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.
What do the server tags on [JP][PVE] BalloonBear [gahu3] mean?
The game's server browser picks up these tags from [JP][PVE] BalloonBear [gahu3]: gmrust (Game mode): Survival, standard Rust style; mp30 (Max players): Slots: 30; ts8 (Group limit): This uses the default limit of 8 players per team; v2635 (Protocol): You need the same game version to get in: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^p (PvE): Here the world is the threat, and players don't fight each other; ^o (Oxide): Oxide (uMod), a plugin framework, is what it runs; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue and world age are in the tags too, displayed at the top of this page.
Population
How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?
A seven-day player-hours placing of #4,089 puts [JP][PVE] BalloonBear [gahu3] in the top 18% of all ranked servers.
How many players are on [JP][PVE] BalloonBear [gahu3] right now?
0 players are on [JP][PVE] BalloonBear [gahu3] at the moment, out of 30 slots. Averaging 0 players across seven days, it topped out at 6. Look at 15:00 UTC: that was the busiest point of the last 48 hours, at 0 players on average.
Server facts
Is [JP][PVE] BalloonBear [gahu3] online, and how reliable is it?
Right now, [JP][PVE] BalloonBear [gahu3] is up and running. Based on the uptime it reports, the last restart was about 2 days 17 hours ago. Out of 168 hours in the last 7 full days, it was online for 168, a 100% uptime. Rust Pop Watch's first record of it is 13 September 2026.
Does [JP][PVE] BalloonBear [gahu3] run smoothly?
The 48-hour average was 194 server fps, with a low of 105. At its peak it held 50,670 entities: buildings, deployables and all the rest. Memory use peaked at 2,373 MB. Players feel lag when fps drops and the entity count climbs.
Where is [JP][PVE] BalloonBear [gahu3] located?
Its name points to Asia, although [JP][PVE] BalloonBear [gahu3] publishes no region tag. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. You'll find it at 126.77.90.98:28020.
Which Rust version is [JP][PVE] BalloonBear [gahu3] on?
On Windows, [JP][PVE] BalloonBear [gahu3] runs Rust network protocol 2635 and build 168909. Joining requires your game to match the protocol, which Steam updates for you.
Wipe times
What happens on [JP][PVE] BalloonBear [gahu3] when wipe day comes around?
Recent wipes averaged a peak of 6 players at their busiest. 40 hours after the latest wipe, the crowd hit its peak.
What is the wipe schedule on [JP][PVE] BalloonBear [gahu3]?
The record of [JP][PVE] BalloonBear [gahu3]'s wipes is still too thin to show its rhythm. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. Its current world has been live for 16 days.
The rules
Which map does [JP][PVE] BalloonBear [gahu3] run?
A procedural map of 3,000 with seed 436589391 is what [JP][PVE] BalloonBear [gahu3] runs, made by the game. RustMaps has it from this page, since identical size and seed give an identical map.
What are the rules and settings 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 fighting other players. It is a Modded listing: plugins or settings change how the game plays. Oxide plugins are running on it. The VAC anti-cheat from Valve is on.
Join up
How do I join [JP][PVE] BalloonBear [gahu3]?
Enter client.connect 126.77.90.98:28020 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.