Local forecast
[JP][PVE] BalloonBear [gahu3]
Online 126.77.90.98:28020 checked 17m ago
Current conditions
observed 17m agoplayers now
0% full
- 7-day average
- 0
- peak 6
- Rank
- #4,094
- top 18%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
Next wipe
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 19:32 UKMon 12 Oct, 18:32 UTC · 15d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
Does [JP][PVE] BalloonBear [gahu3] hold a steady performance?
Across the last 48 hours the average was 196 server fps, with a floor of 105. Buildings, deployables and all else in the world took the entity count to a peak of 50,670. Memory use reached 2,373 MB at its peak. A falling fps and a rising entity count show up to players as lag.
How reliable is [JP][PVE] BalloonBear [gahu3], and is it online now?
Right now [JP][PVE] BalloonBear [gahu3] is up and running. Going by its reported uptime, the last restart was about 2 days 16 hours ago. In the last 7 full days it stayed up 168 of 168 hours, 100% of the time. The first sighting by Rust Wipe Stats was on 13 September 2026.
What location is [JP][PVE] BalloonBear [gahu3] based in?
The name of [JP][PVE] BalloonBear [gahu3] points to Asia, but no region tag is published. Rust Wipe Stats does not look up where the machine stands; it shows where the server says it is. You can reach it at 126.77.90.98:28020.
What version of Rust is running on [JP][PVE] BalloonBear [gahu3]?
Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. To join you need the same protocol, and Steam handles the update.
Server tags
What do [JP][PVE] BalloonBear [gahu3]'s tags tell you?
These are the tags [JP][PVE] BalloonBear [gahu3] publishes for the game's server browser to read: gmrust (Game mode): The mode is plain Rust survival; mp30 (Max players): 30 player slots are available; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Joining needs game protocol 2635 on your copy of the game; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region has been set; ^p (PvE): Player fighting is off; the world supplies the danger; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Modded is its category, with plugins or settings changing the game. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does [JP][PVE] BalloonBear [gahu3] appear among the Rust Wipe Stats lists and filters?
These Rust Wipe Stats lists include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers and Rust PvE servers, live. These filters bring it up 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.
Settings and rules
Which map is in use on [JP][PVE] BalloonBear [gahu3]?
A procedural map of size 3,000 with seed 436589391, generated by the game, runs on [JP][PVE] BalloonBear [gahu3]. From this page RustMaps opens it, since equal size and seed give an equal map.
What settings does [JP][PVE] BalloonBear [gahu3] use, and what rules does it enforce?
Gather rate is not given in the name for [JP][PVE] BalloonBear [gahu3]. No group setting is published, so the game default of 8 players applies. It plays as pve, no combat between players. The server browser lists it as Modded, where plugins or settings alter the game. It runs these plugin frameworks: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe days
On what schedule does [JP][PVE] BalloonBear [gahu3] wipe?
Too few wipes on [JP][PVE] BalloonBear [gahu3] are logged to establish a rhythm. A monthly force wipe hits every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The current map and world began 15 days 22 hours.
What should you expect from wipe day on [JP][PVE] BalloonBear [gahu3]?
Its recent wipes drew an average peak of 6 players. 40 hours after the latest wipe, the crowd hit its peak.
Player counts
How many players does [JP][PVE] BalloonBear [gahu3] hold?
The live count for [JP][PVE] BalloonBear [gahu3]: 0 players, with 30 slots in total. Across the past week it peaked at 6 and averaged 0 players. At 15:00 UTC it was busiest over the past 48 hours, averaging 0 players.
What position does [JP][PVE] BalloonBear [gahu3] hold among Rust servers?
The last seven days of player hours rank [JP][PVE] BalloonBear [gahu3] at #4,094, in the top 18% of ranked servers.
Getting in
What do you do to join [JP][PVE] BalloonBear [gahu3]?
Open the console in Rust with F1, then type client.connect 126.77.90.98:28020 to join. On this page, Launch Rust does the same through Steam.