Skip to the coverage
Live Rust server stats, updated every five minutes.
Rust Live Stats
Live
62,070 players on Rust servers right now 11,772 servers online 3,548 with players on 127 fresh wipes in the last three hours [JP][PVE] BalloonBear [gahu3]: 0 players on now Updated every five minutes

LiveLive coverage · Rust server

[JP][PVE] BalloonBear [gahu3]

Key points

  • 0 of 30 players are on now, 0% full.
  • Over the last seven days it averages 0 players, with a peak of 6.
  • It ranks #4,086, the top 18% of all ranked servers.
  • The current map has been up 16d 3h, since Monday 12 October, 18:32 UTC.
Join
moddedoxidepve

Live coverage

newest first · every post is a reading of this server

Now: 0 of 30 players

0/ 30players now 0% full
07-day averagepeak 6
#4,086ranktop 18%
16d agolast wipeno schedule published
–next wipetoo few wipes seen yet

Players on [JP][PVE] BalloonBear [gahu3]

Players

AveragePeak
00.511.5223:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

How the server is running

Server performance

010020030040023:0008:0017:0001:0010:0020: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.

Rank #4,086 today

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct14 Oct21 Oct28 Oct

Top 18% of all ranked servers. Ranked on player hours over the last seven days.

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

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

Wipes

newest first

Wipe peaks at 6 players

Peak
6
Crowd
–
Lasted
running
Players before
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
【炮炮PVE启蒙】纯净|特色|突袭|技能
EA · groups of 16+ · biweekly · 60 on average
14 / 200
QS『鱼山路』pve|耐玩|升级|突袭
EA · groups of 8+ · 37 on average
41 / 100
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼
EA · groups of 8+ · monthly · 35 on average
34 / 100
Japan Tokyo - Vanilla PvE|JP|Beginner
EA · groups of 16+ · 34 on average
9 / 100
Japan Tokyo - Chill PvE|JP
EA · groups of 16+ · 21 on average
5 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
EA · groups of 8+ · monthly · 21 on average
16 / 88

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on [JP][PVE] BalloonBear [gahu3]?

At their busiest, its recent wipes averaged 6 players. The crowd on the latest wipe peaked 40 hours in.

How often does [JP][PVE] BalloonBear [gahu3] wipe, and at what times?

Too few wipes are recorded for [JP][PVE] BalloonBear [gahu3] to establish a pattern. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 16 days 3 hours have passed since this world was generated.

Tags and filters

Where does [JP][PVE] BalloonBear [gahu3] appear in Rust Live Stats lists and filters?

On Rust Live Stats, [JP][PVE] BalloonBear [gahu3] is listed under Modded Rust servers live now and Rust PvE servers, live now. Under the filters Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.

How should you read the tags on [JP][PVE] BalloonBear [gahu3]?

These are the tags [JP][PVE] BalloonBear [gahu3] makes public: gmrust (Game mode): Standard survival, in the Rust style; mp30 (Max players): The slot count is 30; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code; ^p (PvE): PvE: players do not fight each other, and the world is the danger; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Modded: plugins or changed settings alter the game. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.

Player numbers

What is the current population on [JP][PVE] BalloonBear [gahu3]?

0 of [JP][PVE] BalloonBear [gahu3]'s 30 slots are filled right now. The seven-day average is 0 players, with a peak of 6. The busiest hour in the past 48 was 15:00 UTC, averaging 0 players.

Where does [JP][PVE] BalloonBear [gahu3] sit in the server rankings?

On player hours for the past seven days, [JP][PVE] BalloonBear [gahu3] sits at #4,086, inside the top 18% of ranked servers.

Rules and settings

What settings and rules does [JP][PVE] BalloonBear [gahu3] run?

No gather rate appears in the name [JP][PVE] BalloonBear [gahu3]. No custom limit is set, so groups hold the default 8 players. pve applies here, no fighting other players. Plugins or settings change the game, and the browser lists it as Modded. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.

Which map is in use on [JP][PVE] BalloonBear [gahu3]?

[JP][PVE] BalloonBear [gahu3] runs a game-generated procedural map: size 3,000, seed 436589391. Same size, same seed, same map: RustMaps has it, reachable from this page.

Server facts

Which region is [JP][PVE] BalloonBear [gahu3] hosted in?

The name points to Asia even though [JP][PVE] BalloonBear [gahu3] publishes no region tag. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 126.77.90.98:28020 is its address.

What is performance like on [JP][PVE] BalloonBear [gahu3]?

Server fps averaged 192 over the last 48 hours, with a low of 105. Entity count reached 50,670: buildings, deployables and the rest of the world. Up to 2,373 MB of memory was used. A climbing entity count and low fps are felt as lag by players.

What Rust version is [JP][PVE] BalloonBear [gahu3] on?

Rust network protocol 2635 and build 168909 on Windows is what [JP][PVE] BalloonBear [gahu3] runs. To join, your game must use the same protocol; Steam handles the update for you.

How reliable is [JP][PVE] BalloonBear [gahu3], and is it online at the moment?

[JP][PVE] BalloonBear [gahu3] is up and running at this moment. The uptime it reports puts the last restart at about 2 days 21 hours ago. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. On 13 September 2026, Rust Live Stats saw it for the first time.

How to join

How do you get onto [JP][PVE] BalloonBear [gahu3]?

Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 126.77.90.98:28020.

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, in the Rust style.
mp30
Max players The slot count is 30.
ts8
Group limit 8 per team at most, the game's default setting.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet, the game's usual network layer, carries this server.
$r?
Region code The server sets no region code.

Gameplay

^p
PvE PvE: players do not fight each other, and the world is the danger.

Mods and access

^o
Oxide It runs the plugin framework Oxide (uMod).
^z
Modded Modded: plugins or changed settings alter 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.