Artist page · Modded · on air
[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 10m ago
- Last week
- No. 4,815
- Peak
- No. 3,229
- Days on chart
- 37
Rank
- 21 Sep3,654
- 28 Sep4,063
- 5 Oct9,143
- 15 Oct4,040
- 22 Oct4,815
- now4,088
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
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.
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
- 1 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 58/ 200
- 2 QS『鱼山路』pve｜耐玩｜升级｜突袭 44/ 100
- 3 [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本 38/ 100
- 4 Japan Tokyo - Vanilla PvE|JP|Beginner 28/ 100
- 5 Japan Tokyo - Chill PvE|JP 21/ 100
- 6 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 17/ 88
Quick answers
Reset schedule
What should you expect on [JP][PVE] BalloonBear [gahu3] when wipe day comes?
Averaged over its recent wipes, the crowd reached 6 at the peak. It took 40 hours from the latest wipe for the crowd to peak.
When does [JP][PVE] BalloonBear [gahu3] wipe?
No rhythm can be read yet from the wipes on record for [JP][PVE] BalloonBear [gahu3]. Next up on the wipe calendar is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been on this world for 16 days 12 hours.
Lists and filters
Where does [JP][PVE] BalloonBear [gahu3] appear in Rust Server Rank lists and filters?
These Rust Server Rank lists feature [JP][PVE] BalloonBear [gahu3]: Modded Rust server rankings and Rust PvE servers, ranked. 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 [JP][PVE] BalloonBear [gahu3]'s tags tell you?
Here are the tags [JP][PVE] BalloonBear [gahu3] publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp30 (Max players): The slot count is 30; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): Protocol 2635 is required, so your game must be on that version; cs168909 (Build): The build is 168909; ptrak (Networking): It runs on RakNet, Rust's usual network layer; $r? (Region code): The region code is left blank; ^p (PvE): The world is the danger here: players do not fight each other; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Modded is where it is listed, because plugins or settings change the game. You'll also find the current player count, the queue and when the world was made in the tags, shown at the top of this page.
Settings
Which map is in play on [JP][PVE] BalloonBear [gahu3]?
The map on [JP][PVE] BalloonBear [gahu3] is procedural, size 3,000, seed 436589391, generated by the game. Same size and seed, same map, which RustMaps can show you from this page.
What rules apply on [JP][PVE] BalloonBear [gahu3], and what settings does it use?
No gather rate appears in [JP][PVE] BalloonBear [gahu3]'s name. 8 players is the group limit, the default in the game. It runs pve, other players cannot fight you. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugins running here: Oxide. The VAC anti-cheat from Valve is on.
Server details
What Rust version is [JP][PVE] BalloonBear [gahu3] on?
The setup is Rust network protocol 2635 and build 168909 on Windows, and that is [JP][PVE] BalloonBear [gahu3]. Steam keeps it updated, but your game has to be on the same protocol to join.
How dependable is [JP][PVE] BalloonBear [gahu3], and is it online?
Right now [JP][PVE] BalloonBear [gahu3] is up and taking players. Its own uptime figure puts the last restart at roughly 3 days 7 hours ago. 167 of 168 hours is 99% of the time over the last 7 full days. The first sighting here was on 13 September 2026, logged by Rust Server Rank.
How smoothly does [JP][PVE] BalloonBear [gahu3] run?
Its average over the last 48 hours was 191 server fps; 105 was the lowest it went. The world carried as many as 50,670 entities, buildings and deployables among them. Memory use reached 2,619 MB at its peak. What you feel as lag is low fps and an entity count on the way up.
Where in the world is [JP][PVE] BalloonBear [gahu3] based?
Its name points to Asia, though [JP][PVE] BalloonBear [gahu3] publishes no region tag. What Rust Server Rank shows is where a server says it is, not where the machine stands, which it does not look up. You'll find it at 126.77.90.98:28020.
Numbers
Is [JP][PVE] BalloonBear [gahu3] a busy server?
Of 30 slots on [JP][PVE] BalloonBear [gahu3], 0 are taken at the moment. It peaked at 6 players in the last seven days, averaging 1. Its busiest hour in the last 48 hours was 03:00 UTC, when it averaged 1 players.
What position does [JP][PVE] BalloonBear [gahu3] hold among Rust servers?
A seven-day player-hours count places [JP][PVE] BalloonBear [gahu3] at #4,067 across every ranked server, within the top 18%.
How to join
How do you get into [JP][PVE] BalloonBear [gahu3]?
In Rust, press F1 and enter client.connect 126.77.90.98:28020 in the console. Launch Rust on this page is the other way: it opens the game through Steam and connects you.