[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 10m ago
Server instruments
last reading Tue 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 138 · below 20 is lag, below 10 is badEntities
48 h range 44,041–50,681 · memory 1,961 MBUptime
1 days 18 hours since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 18:32 UTC15d 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
the same kind of game, then region, group limit, rate and wipes- 36/200
- 26/100
- 37/100
- 21/100
- 6/100
- 19/88
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on [JP][PVE] BalloonBear [gahu3]?
At their busiest, its recent wipes drew 6 players on average. Peak crowd on the latest wipe: 40 hours in.
What wipe timing does [JP][PVE] BalloonBear [gahu3] follow?
The rhythm of [JP][PVE] BalloonBear [gahu3]'s wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 15 days ago.
Tag meanings
Which tags does [JP][PVE] BalloonBear [gahu3] carry, and what do they mean?
These are the tags [JP][PVE] BalloonBear [gahu3] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp30 (Max players): Slots: 30; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show [JP][PVE] BalloonBear [gahu3]?
These Rust Metrics lists carry [JP][PVE] BalloonBear [gahu3]: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
Where does [JP][PVE] BalloonBear [gahu3] sit in the rankings?
Player hours over seven days put [JP][PVE] BalloonBear [gahu3] at #4,016, in the top 18% of all ranked servers.
What player count does [JP][PVE] BalloonBear [gahu3] carry?
0 of 30 slots are filled on [JP][PVE] BalloonBear [gahu3] right now. Seven-day check: 1 players on average. Peak reading: 6. The last 48 hours peaked at 03:00 UTC, averaging 2 players at that hour.
Server
Which location does [JP][PVE] BalloonBear [gahu3] run from?
Reading: location. Nothing in the tags, but the name of [JP][PVE] BalloonBear [gahu3] points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 126.77.90.98:28020.
What Rust version is [JP][PVE] BalloonBear [gahu3] on?
Rust network protocol 2635 and build 168909 on Windows is the build [JP][PVE] BalloonBear [gahu3] runs. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for [JP][PVE] BalloonBear [gahu3]?
Check: fps. Average 205 server fps over the last 48 hours, low of 138. Within range. Reading: 50,681 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,365 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is [JP][PVE] BalloonBear [gahu3] up, and how often does it stay up?
[JP][PVE] BalloonBear [gahu3] reports online. Status: normal. Reading: uptime. About 42 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does [JP][PVE] BalloonBear [gahu3] enforce, and what are its settings?
Check: gather rate. The name [JP][PVE] BalloonBear [gahu3] does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: fighting between players is off. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on [JP][PVE] BalloonBear [gahu3]?
Size 3,000 and seed 436589391: the game generates the procedural map on [JP][PVE] BalloonBear [gahu3] from them. The map repeats when size and seed match. Open it on RustMaps from this page.
How to join
What do you do to join [JP][PVE] BalloonBear [gahu3]?
To join: start Rust, press F1 and type client.connect 126.77.90.98:28020. Or press Launch Rust here and Steam opens the game and connects you.