Offline 92.33.153.103:28015 checked 4d ago
Heimdall Busy Save Test
Connect
srv = rust.server("92.33.153.103:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 00:42 UTC20d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 92.33.153.103:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:01 UTC
- hostname
- –
- first seen
- 8 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 543 on average | 677/725 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 438/475 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 308 on average | 38/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 308 on average | 52/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 268 on average | 218/250 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 266 on average | 144/175 |
Quick answers
From the figures on this page.
Population data
What position does Heimdall Busy Save Test take in the server rankings?
Over the last seven days Heimdall Busy Save Test sits at #15,432 on player hours, in the top 69% of ranked servers.
How many players does Heimdall Busy Save Test hold at once?
The current row shows Heimdall Busy Save Test offline; the last response was 4 days 2 hours ago. Over the last seven days it averaged 0 players.
Server facts
What Rust version does Heimdall Busy Save Test run?
The build is Rust network protocol 2634 and build 167058 on Windows, run by Heimdall Busy Save Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Heimdall Busy Save Test, and is it online now?
The latest sample has Heimdall Busy Save Test offline, with a last sighting 4 days 2 hours ago. Over the last 7 full days the hours up number 9 of 168, 5%. Its earliest recorded date in Rust Data is 8 October 2026.
Where does Heimdall Busy Save Test sit?
There is no region published for Heimdall Busy Save Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 92.33.153.103:28015 is its address.
Settings and map
Which rules apply on Heimdall Busy Save Test, and what settings?
No gather rate appears in the name: Heimdall Busy Save Test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
On what schedule does Heimdall Busy Save Test wipe?
The record for Heimdall Busy Save Test holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 19 hours ago.
On Heimdall Busy Save Test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Heimdall Busy Save Test appear among Rust Data lists and filters?
The Rust Data lists that Heimdall Busy Save Test fits are: Rust community servers, unfiltered. 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.
How should you read the server tags on Heimdall Busy Save Test?
The game's server browser reads these tags from Heimdall Busy Save Test: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into Heimdall Busy Save Test?
Enter client.connect 92.33.153.103:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.