On air · chart position #4,088
[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 9m ago
Players
[JP][PVE] BalloonBear [gahu3]
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
Quick answers
Host and version
Is [JP][PVE] BalloonBear [gahu3] online, and how reliable is it?
[JP][PVE] BalloonBear [gahu3] is up as you read this. About 3 days ago is when it last restarted, to go by the uptime it reports. It stayed up 99% of the last 7 full days, 167 of 168 hours. Its earliest entry with Rust Charts dates from 13 September 2026.
Where is [JP][PVE] BalloonBear [gahu3] located?
Without a region tag, [JP][PVE] BalloonBear [gahu3] still has a name that points to Asia. Where a server says it is — that's what Rust Charts shows, without checking the machine's real location. Connect at 126.77.90.98:28020.
Which version of Rust does [JP][PVE] BalloonBear [gahu3] run?
Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. Your game must match the protocol to get in, and Steam keeps it updated for you.
Does [JP][PVE] BalloonBear [gahu3] run smoothly?
Never under 105, and 193 server fps on average, is how the last 48 hours went. Buildings, deployables and all the rest of the world came to as many as 50,670 entities. Memory use peaked at 2,619 MB. Lag, as players experience it, is low fps plus entities piling up.
Who is on
How busy is [JP][PVE] BalloonBear [gahu3]?
On [JP][PVE] BalloonBear [gahu3], 0 players are in and 30 slots are the ceiling. Over the last week it averaged 0 players; the high point was 6. The busiest stretch of the last 48 hours came at 15:00 UTC, averaging 0 players.
How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?
In the seven-day player hours table, [JP][PVE] BalloonBear [gahu3] is #4,088, inside the top 18% of all ranked servers.
Wipe days
What does wipe day look like on [JP][PVE] BalloonBear [gahu3]?
The busiest point of its recent wipes averaged 6 players. 40 hours into the latest wipe, the crowd reached its peak.
What is the wipe schedule on [JP][PVE] BalloonBear [gahu3]?
Too few wipes on record for [JP][PVE] BalloonBear [gahu3] to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and it covers every Rust server. The world it runs now dates from 16 days 6 hours.
Rules and world
What are the rules and settings on [JP][PVE] BalloonBear [gahu3]?
No gather rate appears in the name [JP][PVE] BalloonBear [gahu3]. The default group size of 8 players applies here. You play pve, other players cannot be fought. Modded in the server browser is where it sits; plugins or settings alter the game. Oxide plugins are running on it. VAC is on: that is Valve's anti-cheat.
Which map does [JP][PVE] BalloonBear [gahu3] run?
[JP][PVE] BalloonBear [gahu3] runs a procedural map of size 3,000 with seed 436589391, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Tag guide
Which Rust Charts lists and filters include [JP][PVE] BalloonBear [gahu3]?
The Rust Charts lists that carry [JP][PVE] BalloonBear [gahu3] are: Modded Rust servers and Rust PvE servers. It appears under these filters 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?
gmrust (Game mode): Standard survival rules apply; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only if your game matches that version; cs168909 (Build): Build 168909 is what runs here; ptrak (Networking): RakNet is the network layer here, the game's default; $r? (Region code): The region code is unset; ^p (PvE): PvE, so the danger comes from the world rather than from players; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): This one is modded, so plugins or settings alter play — that's the set of tags [JP][PVE] BalloonBear [gahu3] publishes for the server browser. At the top of this page you'll see the tags' extra details: players now, the queue, and the age of the world.
Join details
How do I join [JP][PVE] BalloonBear [gahu3]?
Enter client.connect 126.77.90.98:28020 in the console, which F1 opens once Rust is running. Launch Rust and join on this page is the other way: Rust opens through Steam and connects you.