Rust Data LabData lab · live
Live readings Servers11,808 Players76,491 Populated3,745 Fresh wipes · 3h114 Sampled every 5 min

Element card · group Community · atomic number 15,348, its rank

Heimdall Busy Save Test

Offline 92.33.153.103:28015 checked 4d ago

Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak –
Rank · atomic number#15,348top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

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.

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

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 572
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 553 on average 572/ 675
  2. 2 Ru Rustoria.co - … 363
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 363/ 525
  3. 3 Ru Rusty Moose |E… 43
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 297 on average 43/ 250
  4. 4 Ru Rustoria.co - … 45
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 296 on average 45/ 250
  5. 5 Ru Rustafied.com … 119
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 272 on average 119/ 200
  6. 6 Ru Rustoria.co - … 140
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 253 on average 140/ 300

Quick answers

from the figures on this page

Settings and map

What rules has Heimdall Busy Save Test set, and what settings are in force?

The name of Heimdall Busy Save Test carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Raids and player fights are part of play here. The server browser lists it under Community. The VAC anti-cheat from Valve is enabled.

Server details

Which location is Heimdall Busy Save Test based in?

There is no region on record for Heimdall Busy Save Test. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. You will find it at 92.33.153.103:28015.

Which Rust version is Heimdall Busy Save Test on?

On Windows, Heimdall Busy Save Test is running Rust network protocol 2634 and build 167058. The protocol must match for you to join; Steam will update your game.

How dependable is Heimdall Busy Save Test for staying online?

Heimdall Busy Save Test is not online at the moment; the last sighting was 4 days 10 hours ago. For the last 7 full days, 9 of 168 hours were online, giving 5% uptime. On 8 October 2026, Rust Data Lab saw it for the first time.

Wipes and resets

How often does a wipe happen on Heimdall Busy Save Test, and at what time?

Too few wipes are on record for Heimdall Busy Save Test to reveal a rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it is running now dates from 27 days 2 hours ago.

On Heimdall Busy Save Test, what happens when wipe day arrives?

Recent wipes on average reached 1 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Tags, lists

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

gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Player slots: 10; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): To join, your game must match protocol 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank: that is the tag list Heimdall Busy Save Test publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does Heimdall Busy Save Test appear in?

These themed Rust Data Lab lists carry Heimdall Busy Save Test: Rust community servers, measured. 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 numbers

What position does Heimdall Busy Save Test hold among Rust servers?

The seven-day player-hours table has Heimdall Busy Save Test at #15,348, in the top 69% of ranked servers.

How full is Heimdall Busy Save Test right now?

No live signal from Heimdall Busy Save Test right now, which was last seen 4 days 10 hours ago. Over seven days the mean player count is 0.

How to join

What steps get you onto Heimdall Busy Save Test?

Open the console with F1 in Rust and type client.connect 92.33.153.103:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players Player slots: 10.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol To join, your game must match protocol 2634.
cs167058
Build Build number: 167058.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

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.