[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 12m ago
Players now
Live- Full
- 3%
- In queue
- 0
- Peak, 48 hours
- 2
- Peak, 7 days
- 6
3% full
Rank
top 18%
7-day average
peak 6
Last wipe
no schedule published
Next wipe
too few wipes seen yet
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.
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 | 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- 1 96/ 200
- 2 9/ 100
- 3 40/ 100
- 4 65/ 100
- 5 30/ 100
- 6 20/ 88
Quick answers
from the figures on this pageServer details
Is [JP][PVE] BalloonBear [gahu3] online, and how reliable is it?
Right now [JP][PVE] BalloonBear [gahu3] is running. The uptime it reports puts its last restart about 3 days 13 hours ago. Over the last 7 full days, 167 of 168 hours were online: 99%. Our records for it start on 13 September 2026, when Rust Dashboard first saw it.
Which version of Rust does [JP][PVE] BalloonBear [gahu3] run?
Rust network protocol 2635 and build 168909 is running on [JP][PVE] BalloonBear [gahu3], which sits on Windows. Joining needs the same protocol on your side, and Steam handles that update.
Where is [JP][PVE] BalloonBear [gahu3] located?
There is no region tag on [JP][PVE] BalloonBear [gahu3], but the name suggests Asia. The location shown at Rust Dashboard is the one the server states; no lookup of the machine's position happens. You'll connect at 126.77.90.98:28020.
Does [JP][PVE] BalloonBear [gahu3] run smoothly?
Across the last 48 hours the average was 190 fps, with a floor of 105. At its highest the count reached 50,499 entities: buildings, deployables and the rest. It drew as much as 2,638 MB of memory at peak. A low fps figure and an entity count that keeps rising are what lag feels like to players.
Tags
Which Rust Dashboard lists and filters include [JP][PVE] BalloonBear [gahu3]?
These Rust Dashboard lists include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers, live now and Rust PvE servers. These filters bring it up 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 browser in the game reads gmrust (Game mode): Standard Rust survival is the game mode; mp30 (Max players): 30 is the slot count; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): The game protocol is 2635; your build has to match it to join; cs168909 (Build): This one runs game build 168909; ptrak (Networking): The game's standard network layer, RakNet, carries this server; $r? (Region code): This server sets no region code; ^p (PvE): Players do not fight each other here; the world is the danger; ^o (Oxide): This server runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it appears under Modded from [JP][PVE] BalloonBear [gahu3] as its tags. At the top of this page you'll find the current players, the queue and the world's creation time, which the tags carry too.
Player counts
How busy is [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] has 1 of its 30 slots filled at the moment. Its seven-day average is 1 players, and it reached 6 at the highest. It was busiest at 03:00 UTC over the last 48 hours, when it averaged 1 players.
How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?
Ranked #4,042 on the last seven days of player hours, [JP][PVE] BalloonBear [gahu3] is in the top 18% of all ranked servers.
Reset times
What does wipe day look like on [JP][PVE] BalloonBear [gahu3]?
At their busiest, its recent wipes drew 6 players on average. Peak crowd on the latest wipe came 40 hours after it began.
What is the wipe schedule on [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] has too few wipes on record yet for its rhythm to be seen. A force wipe comes once a month for all Rust servers, next on Thursday 5 November at 19:00 UTC. The world it runs now dates from 16 days 19 hours ago.
Rules
What are the rules and settings on [JP][PVE] BalloonBear [gahu3]?
You will not find a gather rate in the name of [JP][PVE] BalloonBear [gahu3]. The group limit is 8 players, which is the game's default. It runs pve, no PvP between players. Modded is its category in the browser, because plugins or settings change the game. Oxide plugins are loaded. VAC is on: that is Valve's anti-cheat.
Which map does [JP][PVE] BalloonBear [gahu3] run?
A procedural map of size 3,000 with seed 436589391 is what [JP][PVE] BalloonBear [gahu3] runs, generated by the game. Size and seed fix the map, so this page can show it on RustMaps.
Join
How do I join [JP][PVE] BalloonBear [gahu3]?
The console in Rust opens with F1, and client.connect 126.77.90.98:28020 goes in there. Launch Rust on this page is the other route, opening Rust through Steam to connect you.