Online 126.77.90.98:28020 checked 9m ago
[JP][PVE] BalloonBear [gahu3]
Connect
srv = rust.server("126.77.90.98:28021")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.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 · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 18:32 UTC16d ago | 6 | NaN | 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.
display(srv.map, srv.info())Map
3000 · seed 436589391![Map of [JP][PVE] BalloonBear [gahu3]](https://files.facepunch.com/rust/map-images/d6761dfd08070763448ea77a26593c19fb854b68b428aff9398e7fd1cb5023af/proceduralmap.3000.1791829942846.289_d6761dfd08070763448ea77a26593c19.jpg)
- map
- Procedural Map
- size
- 3000
- seed
- 436589391
Server
srv.info()- address
- 126.77.90.98:28020
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 18:32 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 60 on average | 16/200 |
| 1 | QS『鱼山路』pve｜耐玩｜升级｜突袭 | EA · groups of 8+ · 37 on average | 41/100 |
| 2 | [坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 | EA · groups of 8+ · monthly · 35 on average | 34/100 |
| 3 | Japan Tokyo - Vanilla PvE|JP|Beginner | EA · groups of 16+ · 34 on average | 12/100 |
| 4 | Japan Tokyo - Chill PvE|JP | EA · groups of 16+ · 21 on average | 8/100 |
| 5 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 21 on average | 15/88 |
Quick answers
From the figures on this page.
Population
What position does [JP][PVE] BalloonBear [gahu3] take in the server rankings?
Player hours over seven days put [JP][PVE] BalloonBear [gahu3] at #4,086, in the top 18% of the ranked set.
How many players does [JP][PVE] BalloonBear [gahu3] hold at once?
[JP][PVE] BalloonBear [gahu3] reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 6. The 48-hour sample puts the busiest hour at 15:00 UTC, averaging 0 players.
Server data
How well does [JP][PVE] BalloonBear [gahu3] perform?
Server fps over the last 48 hours averages 192; the floor is 105. Buildings, deployables and all else in the world took the count as high as 50,670 entities. A high of 2,376 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on [JP][PVE] BalloonBear [gahu3]?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [JP][PVE] BalloonBear [gahu3]. The protocol has to match before you can join, and Steam does the updating.
Is [JP][PVE] BalloonBear [gahu3] up, and what does its uptime show?
The current sample puts [JP][PVE] BalloonBear [gahu3] online. A restart about 2 days 22 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is [JP][PVE] BalloonBear [gahu3] hosted?
Its name points to Asia, but [JP][PVE] BalloonBear [gahu3] publishes no region tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 126.77.90.98:28020 is its address.
Map and rules
Which rules apply on [JP][PVE] BalloonBear [gahu3], and what settings?
The name [JP][PVE] BalloonBear [gahu3] carries no gather rate. No custom cap; the default of 8 players per group stands. pve is the game mode here, and no combat between players. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has [JP][PVE] BalloonBear [gahu3] selected?
The game generates the map on [JP][PVE] BalloonBear [gahu3]: procedural, size 3,000, seed 436589391. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does [JP][PVE] BalloonBear [gahu3] wipe?
The record for [JP][PVE] BalloonBear [gahu3] holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 16 days 4 hours ago, and that is the one in play.
On [JP][PVE] BalloonBear [gahu3], what happens on wipe day?
Recent wipes averaged 6 players at their peak. 40 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does [JP][PVE] BalloonBear [gahu3] appear among Rust Data lists and filters?
The Rust Data lists that [JP][PVE] BalloonBear [gahu3] fits are: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on [JP][PVE] BalloonBear [gahu3]?
The game's server browser reads these tags from [JP][PVE] BalloonBear [gahu3]: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join [JP][PVE] BalloonBear [gahu3]?
The manual route: launch Rust, F1, then client.connect 126.77.90.98:28020. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.