At press time 11,752 servers57,724 players129 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 4,086

[JP][PVE] BalloonBear [gahu3]

Online 126.77.90.98:28020 checked 7m ago

[JP][PVE] BalloonBear [gahu3] is a Rust server. At the last count it had 0 players of a possible 30; over the past week it averaged 0, with a peak of 6. It stands at No. 4,086 of the ranked servers, the top 18%. It last wiped 16d ago. Its own tags class it as modded, oxide, pve.

§ 1Attendance

AveragePeak
00.511.5223:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

§ 2Performance

010020030040023:0008:0017: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.

§ 3Standingthe 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.

§ 4The wipe scheduletoo few wipes seen yet

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

The rhythm
Wipe-day peak6

players, 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.

§ 5The record of wipesnewest 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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 【炮炮PVE启蒙】纯净|特色|突袭|技能16/200 EA · groups of 16+ · biweekly · 60 on average
  2. 2 QS『鱼山路』pve|耐玩|升级|突袭41/100 EA · groups of 8+ · 37 on average
  3. 3 [坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼34/100 EA · groups of 8+ · monthly · 35 on average
  4. 4 Japan Tokyo - Vanilla PvE|JP|Beginner12/100 EA · groups of 16+ · 34 on average
  5. 5 Japan Tokyo - Chill PvE|JP8/100 EA · groups of 16+ · 21 on average
  6. 6 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地15/88 EA · groups of 8+ · monthly · 21 on average

§ 7Questions answeredfrom the figures in this entry

Server details

The Rust version for [JP][PVE] BalloonBear [gahu3]: which one?

Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. The protocol must match on your game to join; the update comes through Steam.

How reliable is [JP][PVE] BalloonBear [gahu3], and is it online now?

[JP][PVE] BalloonBear [gahu3] currently answers as online. The uptime it reports puts the last restart at about 2 days 22 hours ago. In the last 7 full days it was up for 168 of 168 hours, 100% of the time. The first sighting at Rust Server Stats was on 13 September 2026.

What is the performance of [JP][PVE] BalloonBear [gahu3] like?

Server fps averaged 192 over the last 48 hours; the low was 105. Of note: 50,670 entities at the peak, counting buildings, deployables and the rest. Up to 2,376 MB of memory was used. What players feel as lag: fps running low and entities climbing.

In which location does [JP][PVE] BalloonBear [gahu3] sit?

The name of [JP][PVE] BalloonBear [gahu3] points to Asia, though no region tag is published. The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. At 126.77.90.98:28020 stands the address.

Settings and map

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

[JP][PVE] BalloonBear [gahu3] runs a procedural map, generated by the game, of size 3,000 with seed 436589391. Because size and seed fix the map, it can be viewed on RustMaps from here.

The rules and settings of [JP][PVE] BalloonBear [gahu3]: what are they?

Nothing in the name of [JP][PVE] BalloonBear [gahu3] gives a gather rate. The group limit is 8 players, the game's default. Play is pve, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings alter the game. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.

The players

What population does [JP][PVE] BalloonBear [gahu3] carry?

At the latest count [JP][PVE] BalloonBear [gahu3] has 0 players, with 30 slots in total. The seven-day record: an average of 0 players and a peak of 6. The busiest hour of the last 48 was 15:00 UTC, averaging 0 players.

What position does [JP][PVE] BalloonBear [gahu3] hold among Rust servers?

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

The tags and lists

[JP][PVE] BalloonBear [gahu3] sits in which Rust Server Stats lists and filters?

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

The tags on [JP][PVE] BalloonBear [gahu3]: what do they signify?

gmrust (Game mode): The standard survival game; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): 8 to a team, which is the default; v2635 (Protocol): The game version must match protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is set; ^p (PvE): No fighting between players; the world is the threat; ^o (Oxide): Oxide (uMod), a framework for plugins, runs here; ^z (Modded): The game is changed by plugins or settings; the browser lists it as Modded — that is the set of tags [JP][PVE] BalloonBear [gahu3] publishes for the game's browser. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.

Wipe schedule

What is the shape of wipe day on [JP][PVE] BalloonBear [gahu3]?

Across its recent wipes, the busiest point averaged 6 players. 40 hours after the latest wipe, the crowd peaked.

On what schedule does [JP][PVE] BalloonBear [gahu3] wipe?

[JP][PVE] BalloonBear [gahu3]'s rhythm cannot be told yet: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe takes every Rust server, without exception. The world now in play was generated 16 days 4 hours ago.

How to join

How does one connect to [JP][PVE] BalloonBear [gahu3]?

To connect, open the console with F1 in Rust and enter client.connect 126.77.90.98:28020. The Launch Rust and join button on this page does the same through Steam.

§ 8Key to the tagswhat each one means

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

Game

gmrust
Game mode The standard survival game.
mp30
Max players The server holds 30 slots.
ts8
Group limit 8 to a team, which is the default.
v2635
Protocol The game version must match protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is set.

Gameplay

^p
PvE No fighting between players; the world is the threat.

Mods and access

^o
Oxide Oxide (uMod), a framework for plugins, runs here.
^z
Modded The game is changed by plugins or settings; the browser lists it as 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.