Station XX-15409 · no signal
Heimdall Busy Save Test
Offline 92.33.153.103:28015 checked 3d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,409
- top 69%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 00:42 UTC19d ago | M0.0■steady | 1 | – | running | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on Heimdall Busy Save Test?
No gather rate appears in the name of Heimdall Busy Save Test. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on Heimdall Busy Save Test right now?
No players are recorded on Heimdall Busy Save Test at this moment; it is offline, and the last sighting was 3 days 13 hours ago. The population averaged 0 players over the past week.
How does Heimdall Busy Save Test rank against other Rust servers?
The last seven days of player hours place Heimdall Busy Save Test at #15,409, in the top 69% of all ranked servers.
Server facts
How reliably does Heimdall Busy Save Test stay online?
No contact with Heimdall Busy Save Test right now, and the last recorded contact was 3 days 13 hours ago. 9 of 168 hours in the last 7 full days were up time, 5% of the total. On 8 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Heimdall Busy Save Test run from?
No region is published by Heimdall Busy Save Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 92.33.153.103:28015.
What build of Rust does Heimdall Busy Save Test use?
On Windows, Heimdall Busy Save Test runs Rust network protocol 2634 and build 167058. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Heimdall Busy Save Test?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Heimdall Busy Save Test run its wipes?
On record so far are too few of Heimdall Busy Save Test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 26 days 6 hours is how long the current world has been running.
Tags
What do the server tags on Heimdall Busy Save Test mean?
The game's server browser reads the tags Heimdall Busy Save Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167058 (Build): The game build is 167058; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Heimdall Busy Save Test appear?
The Rust Server Trends lists that take in Heimdall Busy Save Test are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
What steps get you onto Heimdall Busy Save Test?
Enter client.connect 92.33.153.103:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.