DWG RG-S4092Server sheetchecked 13m ago
[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 13m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Wipes
| Wiped | Peak | Crowd | Lasted | Players 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
Quick answers
Recorded details
How reliable is [JP][PVE] BalloonBear [gahu3], and is it online now?
At this moment [JP][PVE] BalloonBear [gahu3] is online. Counted from its reported uptime, the last restart was about 2 days 23 hours ago. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
How does [JP][PVE] BalloonBear [gahu3] perform, as measured?
194 server fps on average over the last 48 hours, and never under 105. Counted at its highest: 50,670 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 2,619 MB. What players feel as lag is low fps together with a climbing entity count.
In which location is [JP][PVE] BalloonBear [gahu3] hosted?
No region tag is published by [JP][PVE] BalloonBear [gahu3], but its name points to Asia. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 126.77.90.98:28020.
On which Rust version is [JP][PVE] BalloonBear [gahu3] running?
Rust network protocol 2635 and build 168909 on Windows: that is what [JP][PVE] BalloonBear [gahu3] runs. The same protocol is required for joining, and Steam updates your game to it.
Population
How many players are plotted on [JP][PVE] BalloonBear [gahu3]?
Current player count on [JP][PVE] BalloonBear [gahu3]: 0, of 30 slots. The seven-day mean is 0 players; the peak over the same period is 6. Averaged over the last 48 hours, the player count is highest at 15:00 UTC: 0 players.
In the rankings, which position does [JP][PVE] BalloonBear [gahu3] hold?
Within the top 18% of all ranked servers: [JP][PVE] BalloonBear [gahu3] at #4,092 for player hours, seven days recorded.
Wipe times
What happens on [JP][PVE] BalloonBear [gahu3] on the day of a wipe?
The recent wipes averaged a busiest count of 6 players. 40 hours after the latest wipe, the crowd peaked.
Which times and days are wipes plotted at on [JP][PVE] BalloonBear [gahu3]?
Too few wipes are on record for [JP][PVE] BalloonBear [gahu3] to show its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 16 days 5 hours ago.
Rules and settings
Which rules and settings are recorded for [JP][PVE] BalloonBear [gahu3]?
Gather rate for [JP][PVE] BalloonBear [gahu3]: not stated in the name. Eight players per group: the default for the game. It runs the pve game mode, no fighting other players. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.
Which map has [JP][PVE] BalloonBear [gahu3] loaded?
Size 3,000 with seed 436589391: that is the procedural map [JP][PVE] BalloonBear [gahu3] runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Lists and filters
Where does [JP][PVE] BalloonBear [gahu3] appear among the Rust Graphs lists and filters?
On Rust Graphs, [JP][PVE] BalloonBear [gahu3] is placed in these lists: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meaning is attached to each tag on [JP][PVE] BalloonBear [gahu3]?
gmrust (Game mode): Survival in standard Rust style; mp30 (Max players): 30 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^p (PvE): The world is the danger; players do not fight each other; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags [JP][PVE] BalloonBear [gahu3] publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Connect
By what method do you join [JP][PVE] BalloonBear [gahu3]?
Connect with client.connect 126.77.90.98:28020: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp30,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp30
ts8
v2635
cs168909
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
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.