Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO S SRV11,709online PAX55,398playing OCC3,239with players WIPED 3H162
MODModded traffic
Callsign

BLL4037=

[JP][PVE] BalloonBear [gahu3]

Online 126.77.90.98:28020 checked 5m ago

moddedoxidepve
Clearance · join
Players now 0/ 30 0% full
7-day average1peak 6
Rank#4,037top 18%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet
Track history

Players

AveragePeak
00.511.5211:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Server performance

010020030040011:0020:0005:0013:0023:0008: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 Oct15 Oct22 Oct29 Oct

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

Flight plan

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign PVE016EA · groups of 16+ · biweekly · 58 on average 【炮炮PVE启蒙】纯净|特色|突袭|技能
    Players 63/200
  2. 02MOD
    Callsign QSP016EA · groups of 8+ · 37 on average QS『鱼山路』pve|耐玩|升级|突袭
    Players 48/100
  3. 03MOD
    Callsign PVE015EA · groups of 8+ · monthly · 35 on average [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本
    Players 36/100
  4. 04MOD
    Callsign JPN100EA · groups of 16+ · 34 on average Japan Tokyo - Vanilla PvE|JP|Beginner
    Players 35/100
  5. 05MOD
    Callsign JPN110EA · groups of 16+ · 21 on average Japan Tokyo - Chill PvE|JP
    Players 26/100
  6. 06MOD
    Callsign PVE002EA · groups of 8+ · monthly · 20 on average 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
    Players 15/88
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which Rust Tracker filters and lists carry [JP][PVE] BalloonBear [gahu3]?

On Rust Tracker, [JP][PVE] BalloonBear [gahu3] sits in these lists: PvE servers, tracked live and Modded servers, tracked live. On the server list, these filters bring it up: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Which tags does [JP][PVE] BalloonBear [gahu3] carry, and what do they mean?

These tags are published by [JP][PVE] BalloonBear [gahu3] for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp30 (Max players): Slots: 30; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): No region code is set; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What happens on [JP][PVE] BalloonBear [gahu3] on wipe day?

Recent wipes averaged a peak of 6 players. The peak on the latest wipe came 40 hours after it.

Which wipe times are confirmed for [JP][PVE] BalloonBear [gahu3]?

Too few wipes on record for [JP][PVE] BalloonBear [gahu3] to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 16 days 15 hours since this world was made.

Location and Status

What is the uptime on [JP][PVE] BalloonBear [gahu3], and is it online?

[JP][PVE] BalloonBear [gahu3] is up and online at this moment. About 3 days 9 hours ago it restarted last, based on reported uptime. 167 of 168 hours up over the last 7 full days: 99% uptime. First contact for Rust Tracker: 13 September 2026.

Which Rust build is [JP][PVE] BalloonBear [gahu3] running?

Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. The same protocol is required to join, and Steam updates it for you.

How smoothly does [JP][PVE] BalloonBear [gahu3] run?

Server fps held an average of 190 across the last 48 hours, never below 105. Maximum entities carried: 50,499, from buildings and deployables to everything else. It drew as much as 2,619 MB of memory. Players feel lag when fps drops and the entity count climbs.

Where does [JP][PVE] BalloonBear [gahu3] sit?

The name of [JP][PVE] BalloonBear [gahu3] points to Asia, though no region tag is published. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 126.77.90.98:28020.

Population

How many players are on [JP][PVE] BalloonBear [gahu3] right now?

[JP][PVE] BalloonBear [gahu3] is at 0 players, capacity 30. Over seven days: average 1, peak 6 players. Busiest window in 48 hours: 03:00 UTC, 1 players on average.

How does [JP][PVE] BalloonBear [gahu3] compare in the rankings?

Seven-day player hours put [JP][PVE] BalloonBear [gahu3] at #4,037, within the top 18% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on [JP][PVE] BalloonBear [gahu3]?

Nothing in [JP][PVE] BalloonBear [gahu3]'s name states a gather rate. 8 players per group is the game's default, and the cap holds. It runs pve, fighting between players is off. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

What map is [JP][PVE] BalloonBear [gahu3] on?

Generated by the game from seed 436589391, the procedural map on [JP][PVE] BalloonBear [gahu3] measures 3,000. Same size, same seed, same map. RustMaps shows it, linked from this page.

How to Join

Which steps join [JP][PVE] BalloonBear [gahu3]?

To connect: start Rust, press F1, enter client.connect 126.77.90.98:28020 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp30
Max players Slots: 30.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code No region code is set.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed 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.