Rust HeatmapInfrared · players
IR live Players39,438 Servers11,623 Warm2,939 Fresh wipes · 3h88 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–30° · slots

[JP][PVE] BalloonBear [gahu3]

Online 126.77.90.98:28020 checked 6m ago

moddedoxidepve
Sp1 · players now 1/ 30
3% full
Li1 · players, the last 48 hours · hourly average, UTCpeak 2°
Tue 08:00flare: a wipe in that hourThu 06:00
1
7-day average
peak 6
#4,067
rank
top 18%
16d ago
last wipe
no schedule published
–
next wipe
too few wipes seen yet
UTC checked 6m ago

Li2Players

AveragePeak
00.511.5208:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Li3Server performance

010020030040008:0017:0002:0011:0021:0006: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.

Li4Rank

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.

Bx1Wipe 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.

6
wipe-day peak
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.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能
EA · groups of 16+ · biweekly · 59 on average
59 / 200
QS『鱼山路』pve|耐玩|升级|突袭
EA · groups of 8+ · 37 on average
44 / 100
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本
EA · groups of 8+ · monthly · 35 on average
37 / 100
Japan Tokyo - Vanilla PvE|JP|Beginner
EA · groups of 16+ · 34 on average
36 / 100
Japan Tokyo - Chill PvE|JP
EA · groups of 16+ · 21 on average
24 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
EA · groups of 8+ · monthly · 20 on average
17 / 88

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on [JP][PVE] BalloonBear [gahu3]?

Its recent wipes drew an average peak of 6 players. The crowd on the latest wipe reached its peak 40 hours in.

What is the wipe schedule on [JP][PVE] BalloonBear [gahu3]?

Its rhythm cannot yet be told: too few of [JP][PVE] BalloonBear [gahu3]'s wipes are on record. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 16 days 12 hours ago the server made the world it is on now.

Population

How busy is [JP][PVE] BalloonBear [gahu3]?

Of 30 slots on [JP][PVE] BalloonBear [gahu3], 1 are in use right now. Averaged over the past week: 1 players, peaking at 6. Its busiest point in the last 48 hours was 03:00 UTC, averaging 1 players.

How does [JP][PVE] BalloonBear [gahu3] rank against other Rust servers?

The top 18% of ranked servers includes [JP][PVE] BalloonBear [gahu3], at #4,067 for player hours over the last seven days.

Settings and rules

Which map does [JP][PVE] BalloonBear [gahu3] run?

The map on [JP][PVE] BalloonBear [gahu3] is procedural, size 3,000 with seed 436589391, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map.

What are the rules and settings on [JP][PVE] BalloonBear [gahu3]?

The name [JP][PVE] BalloonBear [gahu3] does not specify a gather rate. 8 players is the default group size, and that is the limit here. The server runs pve, other players cannot be fought. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins run on this server. VAC is on, which is Valve's anti-cheat.

Server details

Which version of Rust does [JP][PVE] BalloonBear [gahu3] run?

Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. Steam updates your game for you, and the protocol has to match for you to join.

Is [JP][PVE] BalloonBear [gahu3] online, and how reliable is it?

Right now [JP][PVE] BalloonBear [gahu3] shows as online. About 3 days 7 hours ago is when it last restarted, by its own uptime figure. 167 of 168 hours up over the last 7 full days, which is 99%. Rust Heatmap has had it on record since 13 September 2026.

Where is [JP][PVE] BalloonBear [gahu3] located?

No region tag comes from [JP][PVE] BalloonBear [gahu3], but its name points to Asia. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 126.77.90.98:28020.

Does [JP][PVE] BalloonBear [gahu3] run smoothly?

The last 48 hours brought an average of 191 server fps and a floor of 105. Entities peaked at 50,670, counting buildings, deployables and all the rest of the world. At its peak it held 2,619 MB of memory. What players call lag is low fps together with a growing entity count.

Tags

Which Rust Heatmap lists and filters include [JP][PVE] BalloonBear [gahu3]?

The Rust Heatmap lists that [JP][PVE] BalloonBear [gahu3] fits are: Modded Rust servers, by live population and Best Rust PvE servers. You will find it 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.

What do the server tags on [JP][PVE] BalloonBear [gahu3] mean?

gmrust (Game mode): Rust survival, standard rules; mp30 (Max players): The slot count is 30; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): The game build here is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^p (PvE): No player fighting here: the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Listed as Modded, since settings or plugins change the game are the tags [JP][PVE] BalloonBear [gahu3] publishes, and the server browser reads them. The top of this page also shows the tags for players now, the queue and when the world was made.

How to join

How do I join [JP][PVE] BalloonBear [gahu3]?

To join by console, open it with F1 in Rust and enter client.connect 126.77.90.98:28020. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard rules.
mp30
Max players The slot count is 30.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Your game must match protocol 2635 to get in.
cs168909
Build The game build here is 168909.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code The region code is blank.

Gameplay

^p
PvE No player fighting here: the world is the danger.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Listed as Modded, since settings or plugins change the game.

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.