Skip to the page
Every Rust server graded on real, live numbers. 57,310 players on the roll · 11,753 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 28 October 2026 Pupil no. 126.77.90.98:28020
Name of server

[JP][PVE] BalloonBear [gahu3]

RegisterPresentOnline
Region–
Address126.77.90.98:28020
Last checked6m ago
moddedoxidepve
Launch Rust and join
Overall grade

Steady

66 out of 100, the average of 5 subjects

On the class lists: C− (57), with population over 48 hours and no performance mark.

Players now 0/ 30 0% full
7-day average0peak 6
Rank#4,092top 18%
Last wipe16d agono schedule published
Next wipe–too few wipes seen yet

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average 2/ 100 A quiet classroom so far: 0 of 30 on average. Plenty of space to grow.
Standingrank on player hours 82/ 100 Holds a respectable place: #4,092 on player hours.
Uptimehours on the list, last 48 96/ 100 Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours 100/ 100 Runs smoothly: 192 server fps on average.
Wipeskeeping the crowd after a wipe unmarked Too few wipes seen to mark this yet.
Momentumrank now against a week ago 51/ 100 Moving up: up 51 places this week.

A steady term. Strongest in performance (A+); population is the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

AveragePeak
00.511.5223:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

010020030040023:0008:0017:0002:0011:0021: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

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.

Attendance: the wipe record

1 wipe day in the last 16 weeks

W wiped that day F the force wipe · today. From the wipes in the table below.

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.

wipe-day peak6players, 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
WipedPeakCrowdLastedPlayers 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

classmates: the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净｜特色｜突袭｜技能
EA · groups of 16+ · biweekly · 60 on average
16 / 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
13 / 100
Japan Tokyo - Chill PvE|JP
EA · groups of 16+ · 21 on average
10 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地
EA · groups of 8+ · monthly · 21 on average
15 / 88

Quick answers

from the figures on this page

About the server

Where in the world is [JP][PVE] BalloonBear [gahu3]?

No region tag appears for [JP][PVE] BalloonBear [gahu3], but the name suggests Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 126.77.90.98:28020 is the address to use.

How reliable is [JP][PVE] BalloonBear [gahu3], and is it up?

You can join now: [JP][PVE] BalloonBear [gahu3] is online. According to its reported uptime, the last restart was about 2 days 22 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.

How well does [JP][PVE] BalloonBear [gahu3] run?

It never fell below 105 server fps in the last 48 hours, averaging 192. At its peak, it held 50,670 entities, including buildings, deployables and all else in the world. At its highest, it used 2,376 MB of memory. Lag is what players feel when fps is low and the entity count climbs.

On what Rust version does [JP][PVE] BalloonBear [gahu3] sit?

You will find [JP][PVE] BalloonBear [gahu3] on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.

Resets

How frequently does [JP][PVE] BalloonBear [gahu3] wipe its map?

[JP][PVE] BalloonBear [gahu3] has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 16 days 4 hours.

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

Recent wipes have peaked at 6 players on average. The crowd on the latest wipe was largest 40 hours after it began.

Player numbers

Where does [JP][PVE] BalloonBear [gahu3] sit among Rust servers?

In the top 18% of all ranked servers, [JP][PVE] BalloonBear [gahu3] sits at #4,092 for player hours over the last seven days.

How many players does [JP][PVE] BalloonBear [gahu3] usually have?

[JP][PVE] BalloonBear [gahu3] is showing 0 players right now, with 30 slots in total. Averaging 0 players over seven days, it peaked at 6. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 0 players.

Tags and filters

What do [JP][PVE] BalloonBear [gahu3]'s tags stand for?

You'll see [JP][PVE] BalloonBear [gahu3] tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.

Where does [JP][PVE] BalloonBear [gahu3] appear in the Rust Server Score lists and filters?

Rust Server Score lists that include [JP][PVE] BalloonBear [gahu3]: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters 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.

Map and rules

Which rules does [JP][PVE] BalloonBear [gahu3] enforce, and what are its settings?

Nothing in the name of [JP][PVE] BalloonBear [gahu3] states a gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.

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

A procedural map of size 3,000 and seed 436589391, generated by the game, is what [JP][PVE] BalloonBear [gahu3] runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.

How to join

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

Enter client.connect 126.77.90.98:28020 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, played by the standard rules.
mp30
Max players The server holds 30 slots.
ts8
Group limit The limit is 8 per team, the default the game ships with.
v2635
Protocol To get in, your game needs to be on the same version: the protocol is 2635.
cs168909
Build The game build is 168909.
ptrak
Networking This is RakNet: the network layer Rust normally uses.
$r?
Region code No region code has been set.

Gameplay

^p
PvE Players do not fight one another here; the world is the danger.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Because settings or plugins change how it plays, it is listed as Modded.

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.