[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 13m ago
Measurements
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.
Quick answers
Player counts
How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?
By player hours over the last seven days, [JP][PVE] BalloonBear [gahu3] places at #4,076, within the top 18% of ranked servers.
How busy is [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] holds 1 players at the moment, out of 30 slots. Seven days of counting give an average of 1 players and a peak of 6. Look at the last 48 hours and 03:00 UTC stands out: it averaged 1 players.
Lists and tags
What do the server tags on [JP][PVE] BalloonBear [gahu3] mean?
These are the tags [JP][PVE] BalloonBear [gahu3] publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp30 (Max players): You can join up to 30 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is left blank; ^p (PvE): The danger is the world, not other players: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): This server appears under Modded because plugins or settings alter the game. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] appears among the Rust Population lists that follow: Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Wipe notes
What does wipe day look like on [JP][PVE] BalloonBear [gahu3]?
Across its recent wipes the busiest crowds averaged 6 players. Peak came 40 hours into the latest wipe.
What is the wipe schedule on [JP][PVE] BalloonBear [gahu3]?
Its rhythm cannot be told yet: too few of [JP][PVE] BalloonBear [gahu3]'s wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 16 days 11 hours ago.
Map and rules
Which map does [JP][PVE] BalloonBear [gahu3] run?
[JP][PVE] BalloonBear [gahu3] uses a map the game generates, procedural, at size 3,000 with seed 436589391. Size and seed together fix the map, so you can view it on RustMaps from this page.
What are the rules and settings on [JP][PVE] BalloonBear [gahu3]?
No gather rate appears in the name of [JP][PVE] BalloonBear [gahu3]. Eight players per group is the default, and it applies here. pve is what it runs, no player combat. You find it under Modded, since plugins or settings change how it plays. The plugins it runs are Oxide. You play with Valve's anti-cheat on: VAC.
Server details
Which version of Rust does [JP][PVE] BalloonBear [gahu3] run?
On Windows, [JP][PVE] BalloonBear [gahu3] runs Rust network protocol 2635 and build 168909. Steam updates your game automatically, but you need the same protocol to join.
Does [JP][PVE] BalloonBear [gahu3] run smoothly?
It ran at 192 server fps on average over the last 48 hours, and never went below 105. Entities peaked at 50,670, including buildings, deployables and everything else. Up to 2,619 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.
Is [JP][PVE] BalloonBear [gahu3] online, and how reliable is it?
[JP][PVE] BalloonBear [gahu3] is up and running at the moment. About 3 days 5 hours ago, it restarted, according to its uptime. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. On 13 September 2026, Rust Population saw it for the first time.
Where is [JP][PVE] BalloonBear [gahu3] located?
Nothing in the tags says where [JP][PVE] BalloonBear [gahu3] is, but its name points to Asia. The location a server claims is what Rust Population shows, not the place where the machine stands. 126.77.90.98:28020 is where it lives.
Getting in
How do I join [JP][PVE] BalloonBear [gahu3]?
To connect directly, open Rust's console with F1 and type client.connect 126.77.90.98:28020; or press Launch Rust on this page and Steam opens Rust and joins for you.