[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 6m 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
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 6players, last three wipes
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 |
|---|---|---|---|---|
12 OCT 2026Mon 12 Oct, 18:32 UTC15d 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.
Quick answers
From the figures on this page.
Map and rules
What settings and rules does [JP][PVE] BalloonBear [gahu3] run?
You will find no gather rate in the name of [JP][PVE] BalloonBear [gahu3]. The default group limit of 8 players applies. Filed under pve, player combat is not allowed. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in use on [JP][PVE] BalloonBear [gahu3]?
Generated by the game, the procedural map of [JP][PVE] BalloonBear [gahu3] has size 3,000 and seed 436589391. From this page you can view the map on RustMaps; the same size and seed give the same map.
Tags and filters
Which lists and filters on Rust Server Index is [JP][PVE] BalloonBear [gahu3] filed under?
The Rust Server Index lists that include [JP][PVE] BalloonBear [gahu3] are Modded Rust servers, filed by play style and Rust PvE servers, filed A to Z. Filed under these filters 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.
Which tags are attached to [JP][PVE] BalloonBear [gahu3], and what do they stand for?
These are the tags [JP][PVE] BalloonBear [gahu3] publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp30 (Max players): The queue ceiling sits at 30; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): Your client must run protocol 2635 to connect; cs168909 (Build): Build on file: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set; ^p (PvE): The world is the threat here, not other players; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded: the game is changed by plugins or settings. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipes and resets
How does a wipe day run on [JP][PVE] BalloonBear [gahu3]?
Its recent wipes averaged 6 players at peak. The latest wipe peaked 40 hours in.
Which wipe timetable does [JP][PVE] BalloonBear [gahu3] follow?
Its rhythm is not yet clear, since the record holds too few of [JP][PVE] BalloonBear [gahu3]'s wipes. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 15 days 2 hours is when its current world was made.
Players and ranking
Where does [JP][PVE] BalloonBear [gahu3] sit in the rankings?
Filed under rankings: #4,018 for [JP][PVE] BalloonBear [gahu3] on seven-day player hours, top 18% overall.
How many players are on [JP][PVE] BalloonBear [gahu3] at the moment?
[JP][PVE] BalloonBear [gahu3] is currently showing 0 players on 30 slots. The seven-day average is 1 players; the peak reached 6. Over the last 48 hours, 03:00 UTC drew the highest average: 2 players.
Server details
Which Rust build is [JP][PVE] BalloonBear [gahu3] running?
Rust network protocol 2635 and build 168909 on Windows is what you will find on [JP][PVE] BalloonBear [gahu3]. The protocol must match before you can join, and Steam takes care of updating it.
What is the uptime and current status of [JP][PVE] BalloonBear [gahu3]?
Right now [JP][PVE] BalloonBear [gahu3] is up and running. The uptime it reports puts the last restart at about 44 hours ago. Uptime for the last 7 full days came to 100%, 168 hours out of 168. It was first recorded by Rust Server Index on 13 September 2026.
What is performance like on [JP][PVE] BalloonBear [gahu3]?
Averaged over the last 48 hours, server fps was 203, with a low of 105. Buildings, deployables and everything else in the world came to as many as 50,681 entities. The peak memory figure stood at 2,365 MB. A climbing entity count and low fps are felt by players as lag.
What is the location of [JP][PVE] BalloonBear [gahu3]?
No region tag is published by [JP][PVE] BalloonBear [gahu3]; the name it carries points to Asia. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 126.77.90.98:28020.
How to join
What is the way onto [JP][PVE] BalloonBear [gahu3]?
Enter client.connect 126.77.90.98:28020 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp30,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp30
ts8
v2635
cs168909
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.