RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,316 Populated4,103 Fresh wipes 3 h158 Scan5 min
‹ All servers91.40.38.15:28015
Offline Full Queue Fresh wipe Wipe due No query

Balu Test Server

Offline 91.40.38.15:28015 checked 14d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,700top 63%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct4 Oct7 Oct14 Oct17 Oct20 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap6.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Tue 13 OctMon 12 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 16:24 UTC14d ago 1 – running 1
Mon 12 Oct, 03:09 UTC15d ago 1 – 1.6 days 0
Thu 1 Oct, 10:26 UTC26d ago 1 – 10.7 days 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Balu Test Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Balu Test Server follow?

No next wipe can be predicted for Balu Test Server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 14 days 2 hours ago.

Lists and filters

Which tags does Balu Test Server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from Balu Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Balu Test Server appear in Rust Metrics lists and filters?

On Rust Metrics, Balu Test Server sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Balu Test Server hold among Rust servers?

Player hours over seven days put Balu Test Server at #13,700, in the top 63% of all ranked servers.

What player count does Balu Test Server carry?

Reading for Balu Test Server: offline at this moment; last seen 14 days 1 hours ago.

Server

Which location does Balu Test Server run from?

Reading: location. Balu Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 91.40.38.15:28015.

What Rust version is Balu Test Server on?

Reading: Balu Test Server, Rust network protocol 2634 and build 167398, Windows. Matching protocol is required to join. Let Steam update your game.

Is Balu Test Server up, and how often does it stay up?

Check: connection. Balu Test Server is offline at this moment. Last contact was 14 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Map and rules

How is Balu Test Server configured, and what rules are in force?

No gather rate appears in the name: Balu Test Server. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Join

How do you connect to Balu Test Server?

To join: start Rust, press F1 and type client.connect 91.40.38.15:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.