Rust PopulationField survey · Rust servers
Observing 89,289 players 11,829 servers 4,008 with someone on 4 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,323habitat unknownfirst seen 8 Oct 2026

Heimdall Busy Save Test

Offline 92.33.153.103:28015 checked 4d ago

Measurements

Players now
0/ 10
0% full
7-day average
0
peak –
Rank
#15,323
top 69%
Last wipe
27d ago
no schedule published
Next wipe
–
too few wipes seen yet
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

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.

Obs. 3 · standing

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.

Obs. 4 · the wipe cycle

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.

1
wipe-day peak
players, 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 seen

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.

Field questions

Quick answers

from the figures on this page

Population

How does Heimdall Busy Save Test rank against other Rust servers?

By player hours over the last seven days, Heimdall Busy Save Test places at #15,323, within the top 69% of ranked servers.

How busy is Heimdall Busy Save Test?

We have no live count for Heimdall Busy Save Test right now. It was last seen 4 days 9 hours ago. Counted over seven days: an average of 0 players.

Lists and tags

What do the server tags on Heimdall Busy Save Test mean?

What the game's server browser reads from Heimdall Busy Save Test is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): You can join up to 10 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2634 (Protocol): The protocol is 2634; a different version will not connect; cs167058 (Build): Game build: 167058; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include Heimdall Busy Save Test?

Heimdall Busy Save Test appears among the Rust Population lists that follow: Community servers, field-listed. Filter the server list by Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more and it will show up.

Wipe notes

What does wipe day look like on Heimdall Busy Save Test?

Averaged over recent wipes, 1 players were counted at the busiest point. 0 hours after the latest wipe the crowd peaked.

What is the wipe schedule on Heimdall Busy Save Test?

Its rhythm cannot be told yet: too few of Heimdall Busy Save Test's wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 27 days 1 hours ago.

Settings

What are the rules and settings on Heimdall Busy Save Test?

The name tells you nothing about gather rates: Heimdall Busy Save Test states none. Eight players per group is the default, and it applies here. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. A community server, it appears in the Community section of the browser. You play with Valve's anti-cheat on: VAC.

About the server

Which version of Rust does Heimdall Busy Save Test run?

The setup is Rust network protocol 2634 and build 167058 on Windows for Heimdall Busy Save Test. Your game needs the same protocol to join; Steam takes care of updating it.

Is Heimdall Busy Save Test online, and how reliable is it?

We last saw Heimdall Busy Save Test 4 days 9 hours ago, and it is offline now. Over the last 7 full days, 9 of 168 hours were online, or 5%. On 8 October 2026, Rust Population saw it for the first time.

Where is Heimdall Busy Save Test located?

A region is not published by Heimdall Busy Save Test. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 92.33.153.103:28015.

How to join

How do I join Heimdall Busy Save Test?

Either enter client.connect 92.33.153.103:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

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 You can join up to 10 slots.
ts8
Group limit This is the game default: at most 8 per team.
v2634
Protocol The protocol is 2634; a different version will not connect.
cs167058
Build Game build: 167058.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code This server has no region code.

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.