[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 12m 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 17% 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 UTC5d 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
- 63/ 200
- 20/ 100
- 0/ 100
- 25/ 100
- 24/ 100
- 22/ 88
Quick answers
Tags and listings
Where does [JP][PVE] BalloonBear [gahu3] appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers and Go deep on PvE servers. You can find it on the server list by these filters: 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 week.
How should you read the tags on [JP][PVE] BalloonBear [gahu3]?
gmrust (Game mode): Survival, as standard Rust does it; mp30 (Max players): It holds 30 players; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167584 (Build): This server runs build 167584; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^p (PvE): Other players aren't a threat; the world is; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list [JP][PVE] BalloonBear [gahu3] puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the performance like on [JP][PVE] BalloonBear [gahu3]?
The last 48 hours saw an average of 198 server fps, never dropping below 152. The entity count reached a high of 48,291, covering buildings, deployables and everything else. 2,466 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.
Where can you find [JP][PVE] BalloonBear [gahu3]?
There is no region tag on [JP][PVE] BalloonBear [gahu3], but the name hints at Asia. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 126.77.90.98:28020.
Is [JP][PVE] BalloonBear [gahu3] up, and how often does it stay online?
[JP][PVE] BalloonBear [gahu3] is live as of this check. According to its reported uptime, the last restart was about 2 days 22 hours ago. Over the past full 7 days it stayed up for 102 of 168 hours, or 61%. Rust Going Deep has had it on record since 13 September 2026.
What is the Rust version for [JP][PVE] BalloonBear [gahu3]?
Rust network protocol 2634 and build 167584 is what [JP][PVE] BalloonBear [gahu3] runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does [JP][PVE] BalloonBear [gahu3] follow for wipes?
The wipes recorded for [JP][PVE] BalloonBear [gahu3] are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 5 days 1 hours is how long ago this world came into being.
What happens on wipe day at [JP][PVE] BalloonBear [gahu3]?
Across its recent wipes, the average busiest point drew 6 players. 40 hours after the latest wipe started, the crowd hit its peak.
Settings and map
Which rules and settings is [JP][PVE] BalloonBear [gahu3] running?
Its name does not state a gather rate for [JP][PVE] BalloonBear [gahu3]. The group limit is the game's default of 8 players. pve is the game mode, no fighting other players. The server browser puts it under Modded, as plugins or settings alter the game. You will find Oxide plugins installed. VAC, Valve's anti-cheat, is enabled.
What's the map on [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] uses a procedural map of size 3,000 with seed 436589391, made by the game. The map is reproducible from its size and seed, so RustMaps can show it from this page.
Population
How many players are on [JP][PVE] BalloonBear [gahu3]?
[JP][PVE] BalloonBear [gahu3] is holding 0 players on its 30 slots at the moment. For the past week, players averaged 1 with a high of 6. At 05:00 UTC in the last 48 hours, the average reached its highest: 2 players.
Where does [JP][PVE] BalloonBear [gahu3] sit in the rankings?
Over the last seven days, [JP][PVE] BalloonBear [gahu3] is #3,712 by player hours, among the top 17% of all ranked servers.
How to join
What's the way to join [JP][PVE] BalloonBear [gahu3]?
To join, open Rust, hit F1, and enter client.connect 126.77.90.98:28020. Or click Launch Rust on this page to open the game through Steam and connect.