[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 6m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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
every wipe as a delivery, newest first-
Mon 12 Oct, 18:32 UTC 19:32 UK · 16d agoWipe delivered
- Peak
- 6
- Crowd
- –
- Lasted
- running
- Players before
- 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.
- 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 16 / 200
- QS『鱼山路』pve｜耐玩｜升级｜突袭 42 / 100
- [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本 27 / 100
- Japan Tokyo - Vanilla PvE|JP|Beginner 13 / 100
- Japan Tokyo - Chill PvE|JP 9 / 100
- 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 12 / 88
Quick answers
From the figures on this page.
Player count
How does [JP][PVE] BalloonBear [gahu3] compare with other Rust servers in the rankings?
Over the past seven days, [JP][PVE] BalloonBear [gahu3] has climbed to #4,091 for player hours, putting it in the top 18% of all ranked servers.
How many players are on [JP][PVE] BalloonBear [gahu3] right now?
The current count is 0 players on 30 slots for [JP][PVE] BalloonBear [gahu3]. Averaged over the past week: 0 players, peaking at 6. The busiest hour over the last 48 hours was 15:00 UTC, averaging 0 players.
Map and rules
On what map does [JP][PVE] BalloonBear [gahu3] take place?
The game generates the procedural map on [JP][PVE] BalloonBear [gahu3] at size 3,000 with seed 436589391. You can see the map on RustMaps from this page, since one size and seed give one map.
What are the rules on [JP][PVE] BalloonBear [gahu3], and what settings does it run?
No gather rate appears in the name of [JP][PVE] BalloonBear [gahu3]. The game's default applies: 8 players to a group at most. You get pve here, other players cannot be fought. Plugins or settings alter the game on this one, which sits under Modded in the server browser. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
About the server
What is the location of [JP][PVE] BalloonBear [gahu3]?
The name of [JP][PVE] BalloonBear [gahu3] points to Asia, though no region tag is published. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. The address to connect to is 126.77.90.98:28020.
Does [JP][PVE] BalloonBear [gahu3] perform well?
Averaged over the last 48 hours, server fps was 194, with a low of 105. Buildings, deployables and all the rest of the world pushed its entity count as high as 50,670. 2,619 MB of memory was its top figure. Lag, to players, means low fps alongside an entity count on the rise.
What is the uptime of [JP][PVE] BalloonBear [gahu3], and is it online?
[JP][PVE] BalloonBear [gahu3] is up and online at the moment. The uptime it reports puts its last restart at about 2 days 23 hours ago. 86% is the uptime for the last 7 full days, up for 144 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is [JP][PVE] BalloonBear [gahu3] using?
Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. To join, your game must be on the same protocol; Steam handles that update for you.
Wipe times
How does [JP][PVE] BalloonBear [gahu3] handle its wipe days?
6 players is the average peak across its recent wipes. On the latest wipe, 40 hours passed before the crowd peaked.
On what schedule does [JP][PVE] BalloonBear [gahu3] reset its map?
To tell its rhythm we would need more of [JP][PVE] BalloonBear [gahu3]'s wipes on record; there are too few yet. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. You are playing a world created 16 days 5 hours.
Tags and filters
Where does [JP][PVE] BalloonBear [gahu3] appear in Rust Wipe Tracker lists and filters?
These Rust Wipe Tracker lists take [JP][PVE] BalloonBear [gahu3]: Modded Rust servers and Best Rust PvE servers. On the server list, apply Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more and it appears.
How should you read the tags on [JP][PVE] BalloonBear [gahu3]?
The game's server browser picks up these [JP][PVE] BalloonBear [gahu3] tags: gmrust (Game mode): Standard Rust survival is the game mode here; mp30 (Max players): The server has 30 slots; ts8 (Group limit): Team limit: 8, the standard default; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^p (PvE): There's no player combat; the world itself is the threat; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
Connecting
What is the process to join [JP][PVE] BalloonBear [gahu3]?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 126.77.90.98:28020.