Rust Server Analytics 56,681 players11,752 servers
All servers
Drill-through Server detail

[JP][PVE] BalloonBear [gahu3]

Online 126.77.90.98:28020 checked 7m ago

Drill-through
FilterServeris [JP][PVE] BalloonBear [gahu3]
Attributes
moddedoxidepve
Last refreshed
Players now 0/ 30
7-day average 0 peak 6
Rank #4,092 top 18%
Last wipe 16d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.511.5200:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040000:0009:0018:0002:0011:0021:00

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
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct14 Oct21 Oct28 Oct

Top 18% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak6players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 40 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 60 on average 16 / 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average 41 / 100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 35 on average 34 / 100
Japan Tokyo - Vanilla PvE|JP|Beginner EA · groups of 16+ · 34 on average 14 / 100
Japan Tokyo - Chill PvE|JP EA · groups of 16+ · 21 on average 9 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 21 on average 15 / 88

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for [JP][PVE] BalloonBear [gahu3]: what is it?

Too few wipes on record for [JP][PVE] BalloonBear [gahu3] to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 16 days 4 hours ago the current world was made.

Wipe day on [JP][PVE] BalloonBear [gahu3]: what should you expect?

Across recent wipes the busiest point averaged 6 players. Peak population for the latest wipe came 40 hours after it began.

Server

Which location hosts [JP][PVE] BalloonBear [gahu3]?

No region tag is published by [JP][PVE] BalloonBear [gahu3], but the name points to Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 126.77.90.98:28020.

Which Rust version is [JP][PVE] BalloonBear [gahu3] on?

On Windows, [JP][PVE] BalloonBear [gahu3] runs Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam handles the update.

Is [JP][PVE] BalloonBear [gahu3] up, and how steady is its uptime?

The current status of [JP][PVE] BalloonBear [gahu3] is online. Its reported uptime indicates a restart roughly 2 days 22 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.

What performance does [JP][PVE] BalloonBear [gahu3] show?

Over 48 hours the average held at 194 server fps, and the minimum was 105. At its highest the entity count was 50,670, including buildings, deployables and all else. At its highest, memory use was 2,376 MB. Players experience lag as low fps combined with a rising entity count.

Tags

How should the tags on [JP][PVE] BalloonBear [gahu3] be read?

gmrust (Game mode): Survival in the standard Rust format; mp30 (Max players): 30 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^p (PvE): Player combat is off; the world supplies the danger; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings change the game, so it sits under Modded are the tags [JP][PVE] BalloonBear [gahu3] publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature [JP][PVE] BalloonBear [gahu3]?

The following Rust Server Analytics lists count [JP][PVE] BalloonBear [gahu3] among their servers: Modded Rust servers: live data and PvE Rust servers by live population. On the server list, the filters that return it are: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player numbers

Against other Rust servers, how does [JP][PVE] BalloonBear [gahu3] compare?

On player hours over seven days, [JP][PVE] BalloonBear [gahu3] ranks #4,092, within the top 18% of ranked servers.

What is the population of [JP][PVE] BalloonBear [gahu3]?

Population at the current refresh: 0 players on [JP][PVE] BalloonBear [gahu3], against 30 slots. The seven-day mean is 0 players, against a peak of 6. The 48-hour peak window is 15:00 UTC, at an average of 0 players.

Map and rules

How is [JP][PVE] BalloonBear [gahu3] configured, and what rules apply?

No gather rate is given in the name of [JP][PVE] BalloonBear [gahu3]. No custom group limit: 8 players is the standard. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, enabled.

What is the map for [JP][PVE] BalloonBear [gahu3]?

The game generates a procedural map of size 3,000 with seed 436589391 for [JP][PVE] BalloonBear [gahu3]. Size and seed fix the map, so a RustMaps view is available from this page.

How to join

How do you connect to [JP][PVE] BalloonBear [gahu3]?

In the Rust console (F1), enter client.connect 126.77.90.98:28020. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp30,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp30
Max players 30 slots in total.
ts8
Group limit Team cap of 8, the stock game setting.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been set.

Gameplay

^p
PvE Player combat is off; the world supplies the danger.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded Plugins or settings change the game, so it sits under Modded.

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.