Rust StatisticsWorking papers on every public Rust server · 33,332 players now

[JP][PVE] BalloonBear [gahu3]

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 126.77.90.98:28020

Abstract

We describe the public Rust server [JP][PVE] BalloonBear [gahu3], reached at 126.77.90.98:28020. At the last check it held 0 of 30 places, against a seven-day mean of 1 and a peak of 61. It ranks #4,077 of all servers, the top 18%. It last wiped 16d ago.

Keywordsmodded oxide pve

Access. Launch Rust and join ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.
Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/300% full
In the queue0no queue
Seven-day mean1peak 6, 48 h peak 2
Rank2#4,077top 18%
Last wipe16d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.511.5207:0016:0001:0010:0020:0005:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040007:0016:0001:0010:0020:0005:00
Figure 2: 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.

4Rank

The server stands in the top 18% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct15 Oct22 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak6players, last three wipes
02468+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 12 Oct, 18:3216d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of [JP][PVE] BalloonBear [gahu3]
Figure 5: The map: Procedural Map, size 3000, seed 436589391. Open on RustMaps.
Table 4: The server's published settings.
Address126.77.90.98:28020
Region–
Max players30
Group limit8, the default
Wipe schedule–
Last wipe12 Oct 2026, 18:32 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3000
Seed436589391

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2], pve wipes and settings [3] and Rust wipe forecast [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
【炮炮PVE启蒙】纯净｜特色｜突袭｜技能EA · groups of 16+ · biweekly · 59 on average57/200
QS『鱼山路』pve｜耐玩｜升级｜突袭EA · groups of 8+ · 37 on average44/100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼EA · groups of 8+ · monthly · 35 on average33/100
Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 34 on average25/100
Japan Tokyo - Chill PvE|JPEA · groups of 16+ · 21 on average16/100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average18/88

Appendix AQuick answers

From the figures on this page.

Server details

A.1How well does [JP][PVE] BalloonBear [gahu3] run?

Its average server fps over the last 48 hours was 192, with a minimum of 105. Buildings, deployables and all other world objects counted together reached a maximum of 50,670 entities. Its highest memory usage was 2,619 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What is the location of [JP][PVE] BalloonBear [gahu3]?

Its name points to Asia, though [JP][PVE] BalloonBear [gahu3] publishes no region tag. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 126.77.90.98:28020.

A.3What is the reliability of [JP][PVE] BalloonBear [gahu3], and is it online?

[JP][PVE] BalloonBear [gahu3] is currently online. The uptime it reports indicates a restart about 3 days 6 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What version of Rust is run on [JP][PVE] BalloonBear [gahu3]?

The version of Rust on [JP][PVE] BalloonBear [gahu3] is network protocol 2635 and build 168909, and the operating system is Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.5What schedule does [JP][PVE] BalloonBear [gahu3] follow for wipes?

Too few wipes by [JP][PVE] BalloonBear [gahu3] have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 16 days 11 hours have passed since the current world was generated.

A.6What characterises wipe day on [JP][PVE] BalloonBear [gahu3]?

Across its recent wipes, the average peak population was 6 players. The crowd reached its maximum 40 hours after the latest wipe.

Player count

A.7How does [JP][PVE] BalloonBear [gahu3] compare with other Rust servers in the rankings?

Ranked by player hours across seven days, [JP][PVE] BalloonBear [gahu3] holds #4,077, in the top 18% of all ranked servers.

A.8How would you characterise the player activity on [JP][PVE] BalloonBear [gahu3]?

The current population of [JP][PVE] BalloonBear [gahu3] is 0, drawn from 30 slots. Averaged over the last seven days: 1 players; the same period peaks at 6. Averaging 1 players, 03:00 UTC was the busiest hour of the past 48.

Tags, lists

A.9How should the tags on [JP][PVE] BalloonBear [gahu3] be interpreted?

Tags from [JP][PVE] BalloonBear [gahu3], read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp30 (Max players): The slot count is 30; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^p (PvE): The threat is the world, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can [JP][PVE] BalloonBear [gahu3] be found among the Rust Statistics lists and filters?

These Rust Statistics lists include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers and Rust PvE servers: live list. You will find it on the server list filtered by: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.11What are the settings and rules that govern [JP][PVE] BalloonBear [gahu3]?

Its name carries no gather rate for [JP][PVE] BalloonBear [gahu3]. The group cap is 8 players, which is the default in the game. pve is the game mode here; players cannot fight each other. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

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

Generated by the game from seed 436589391, the procedural map on [JP][PVE] BalloonBear [gahu3] measures 3,000. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What steps are required to join [JP][PVE] BalloonBear [gahu3]?

Enter client.connect 126.77.90.98:28020 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp30,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp30Max players. The slot count is 30.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. This server runs game build 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. A region code has not been set.
Gameplay
^pPvE. The threat is the world, not other players.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. Modded listing: plugins or settings modify 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Pve wipes and settings. ruststatistics.org/top-rust-pve-servers.
  4. [4]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.