Skip to the page
Network live 11,749 servers online 55,156 players aboard 134 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Heimdall Busy Save Test

Offline 92.33.153.103:28015 checked 4d ago

Tracking number · connect
Wipe progress · wiped 27d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
0/ 10 players now 0% full
07-day averagepeak –
#15,344ranktop 69%
27d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

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.

Wipes

every wipe as a delivery, newest first
  1. Thu 8 Oct, 00:42 UTC 01:42 UK · 20d ago
    Wipe delivered
    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.

Similar parcels

Similar servers

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

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 553 on average 342 / 375
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 230 / 250
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 294 on average 36 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 293 on average 29 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 273 on average 58 / 100
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 252 on average 79 / 200
Help desk

Quick answers

From the figures on this page.

Population

What is the ranking of Heimdall Busy Save Test against other Rust servers?

A seven-day player-hours count places Heimdall Busy Save Test at #15,344: the top 69% of every ranked server.

What is the current population on Heimdall Busy Save Test?

The last sighting of Heimdall Busy Save Test was 4 days 12 hours ago; it is offline right now. Averaged over the past week: 0 players.

Map and rules

What settings and rules should you know for Heimdall Busy Save Test?

No gather rate appears in the name of Heimdall Busy Save Test. The game's default applies: 8 players to a group at most. It runs survival, gather and build and raid: the standard game. You can raid and fight other players. It appears in the server browser under Community, being a community server. The VAC anti-cheat from Valve is enabled.

About the server

What location does Heimdall Busy Save Test run from?

There is no region published for Heimdall Busy Save Test. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 92.33.153.103:28015.

How reliable is Heimdall Busy Save Test, and is it currently online?

Heimdall Busy Save Test is offline at the moment, with the last sighting 4 days 12 hours ago. 5% is the uptime for the last 7 full days, up for 9 of 168 hours. 8 October 2026 is when Rust Wipe Tracker first recorded it.

On what Rust version does Heimdall Busy Save Test operate?

The version on Heimdall Busy Save Test is Rust network protocol 2634 and build 167058, running on Windows. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

What happens on Heimdall Busy Save Test when wipe day arrives?

1 players is the average peak across its recent wipes. On the latest wipe, 0 hours passed before the crowd peaked.

On what schedule does Heimdall Busy Save Test reset its map?

To tell its rhythm we would need more of Heimdall Busy Save Test's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. You are playing a world created 27 days 5 hours.

Tags and listings

Where does Heimdall Busy Save Test appear in Rust Wipe Tracker lists and filters?

The Rust Wipe Tracker lists that include Heimdall Busy Save Test are: Rust community servers, unmodded. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

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

Read off the game's server browser, the tags for Heimdall Busy Save Test are: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): It holds 10 slots; ts8 (Group limit): Team limit: 8, the standard default; v2634 (Protocol): To join, your game must match protocol 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Getting started

What steps do you take to join Heimdall Busy Save Test?

Enter client.connect 92.33.153.103:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players It holds 10 slots.
ts8
Group limit Team limit: 8, the standard default.
v2634
Protocol To join, your game must match protocol 2634.
cs167058
Build Build number: 167058.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code The region code is unset.

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.