Open every day, at every hour Admission free 11,802 servers and 85,272 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 15,437Acc. 2026.15437

Heimdall Busy Save Test

Rust server · in the archive since 8 October 2026

Offline 92.33.153.103:28015 checked 4d ago

To visit
Players now 0/ 10
0% full
7-day average0peak –
Rank#15,437top 69%
Last wipe26d agoThu 1 Oct, 18:01 UTC · no schedule published
Next wipe–too few wipes seen yet

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectedlast seen, 24 Oct 2026, 10:50 UTCAll times UTC.

The record of each wipe

  1. Thu 8 Oct 202600:42 UTC20d ago
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    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.

The rhythm

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.

1wipe-day peakplayers, 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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

No hourly history yet.

Hourly average and peak, UTC.

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

Folder 3

Rank

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.

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags, lists

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

These tags from Heimdall Busy Save Test, read by the game's server browser, are: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are set on this server; ts8 (Group limit): The default cap of 8 per team applies here; v2634 (Protocol): The server runs game protocol 2634; matching it is required to join; cs167058 (Build): Build number: 167058; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The server has no region code. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.

Which Rust Server History lists and filters include Heimdall Busy Save Test?

The Rust Server History lists that feature Heimdall Busy Save Test are: Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Server entry

Which version of Rust does Heimdall Busy Save Test run?

Rust network protocol 2634 and build 167058 is the build Heimdall Busy Save Test runs, on Windows. Joining requires your game to be on the same protocol; Steam keeps it updated for you.

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

Offline now, Heimdall Busy Save Test was last seen 4 days 4 hours ago. 9 of 168 hours, or 5% of the time, over the last 7 full days. 8 October 2026 is when Rust Server History first saw it.

Where is Heimdall Busy Save Test located?

There is no region published by Heimdall Busy Save Test. Rust Server History does not look up where the machine stands; it shows where a server says it is. Its entry gives 92.33.153.103:28015 as the address.

Wipe history

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

An average peak of 1 players was drawn by its recent wipes. At 0 hours after the latest wipe, the crowd reached its peak.

What is the wipe schedule on Heimdall Busy Save Test?

Its rhythm is not yet clear: too few of Heimdall Busy Save Test's wipes are on record. The monthly force wipe comes next on Thursday 5 November at 19:00 UTC, and every Rust server wipes then. Made 26 days 21 hours ago, the current world is what it runs now.

Player counts

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

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

How busy is Heimdall Busy Save Test?

The last sighting of Heimdall Busy Save Test in the live count was 4 days 4 hours ago; it is offline now. An average of 0 players is recorded across the last seven days.

Map and rules

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

You will not find a gather rate in the name of Heimdall Busy Save Test. At 8 players, the group limit matches the game's default. Recorded as survival, with this note: gather, build, raid: the standard game. PvP and raiding are enabled. The Community section of the server browser carries it. The anti-cheat VAC from Valve is active.

Join record

How do I join Heimdall Busy Save Test?

Press F1 in Rust to open the console, then enter client.connect 92.33.153.103:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players 10 slots are set on this server.
ts8
Group limit The default cap of 8 per team applies here.
v2634
Protocol The server runs game protocol 2634; matching it is required to join.
cs167058
Build Build number: 167058.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The 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.