RUST METRICSFlight deck · live data
Data live Servers11,647 Players49,596 Populated3,216 Fresh wipes 3 h107 Scan5 min
‹ All servers92.33.153.103:28015
Offline Full Queue Fresh wipe Wipe due No query

Heimdall Busy Save Test

Offline 92.33.153.103:28015 checked 3d ago

COM 1 · connect

Server instruments

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

Players now

0% 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#15,396top 69%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
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
15k10k15k20k8 Oct11 Oct14 Oct17 Oct25 Oct28 Oct

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

PLAN

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 peak1players, last three wipes

The first 48 hours of its last wipes

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
Thu 8 Oct, 00:42 UTC20d ago 1 – running 1

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

Wipe schedule

What should you expect from wipe day on Heimdall Busy Save Test?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Heimdall Busy Save Test follow?

To tell the rhythm of Heimdall Busy Save Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 26 days 15 hours ago the current world was made.

Lists and filters

How should you read the tags on Heimdall Busy Save Test?

Tags published by Heimdall Busy Save Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): Game build reading: 167058; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Heimdall Busy Save Test?

These Rust Metrics lists carry Heimdall Busy Save Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Heimdall Busy Save Test sit in the rankings?

Player hours over seven days put Heimdall Busy Save Test at #15,396, in the top 69% of all ranked servers.

What is the population on Heimdall Busy Save Test?

Status for Heimdall Busy Save Test: offline. Last seen 3 days 22 hours ago. Seven-day reading: 0 players on average.

Operator and location

What location is Heimdall Busy Save Test hosted in?

No region comes from Heimdall Busy Save Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 92.33.153.103:28015.

What Rust version is Heimdall Busy Save Test on?

Version check: Rust network protocol 2634 and build 167058 on Windows, run by Heimdall Busy Save Test. To get in, your game needs the same protocol; Steam applies the update.

Is Heimdall Busy Save Test up, and how often does it stay up?

Check: connection. Heimdall Busy Save Test is offline at this moment. Last contact was 3 days 22 hours ago. Reading: 5% uptime over the last 7 full days. It was up 9 of 168 hours. The first sighting on Rust Metrics was 8 October 2026.

Settings and map

What settings and rules apply on Heimdall Busy Save Test?

Check: gather rate. The name Heimdall Busy Save Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Join

How can you get onto Heimdall Busy Save Test?

Press F1 in Rust and enter client.connect 92.33.153.103:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build Game build reading: 167058.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.