Offline 37.48.20.204:28025 checked 6d ago
URHEIM (local)
Connect
srv = rust.server("37.48.20.204:28027")
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, 30 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 04:23 UTC8d ago | 1 | NaN | running | 0 |
# 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 37.48.20.204:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 04:23 UTC
- hostname
- –
- first seen
- 20 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 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
How does URHEIM (local) compare in the rankings?
Over the last seven days URHEIM (local) sits at #15,373 on player hours, in the top 69% of ranked servers.
What population does URHEIM (local) carry?
URHEIM (local) returns no live count at this refresh, having last been seen 6 days 15 hours ago. Over the last seven days it averaged 0 players.
Server data
What is the Rust version on URHEIM (local)?
Rust network protocol 2634 and build 167398 on Windows is what URHEIM (local) runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is URHEIM (local), and is it online now?
Offline now for URHEIM (local), last seen 6 days 15 hours ago. Over the last 7 full days the hours up number 18 of 168, 11%. Its earliest recorded date in Rust Data is 20 October 2026.
Where does URHEIM (local) sit?
For URHEIM (local), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 37.48.20.204:28025 is its address.
Settings and map
What rules and settings are recorded for URHEIM (local)?
No gather rate appears in the name: URHEIM (local). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
What is the map on URHEIM (local)?
URHEIM (local) runs a procedural map, which the game generates.
Wipe data
On what schedule does URHEIM (local) wipe?
A rhythm cannot be read from the wipes of URHEIM (local) on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 8 days 14 hours ago, and that is the one in play.
What is wipe day on URHEIM (local) like?
Recent wipes averaged 1 players at their peak. 30 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold URHEIM (local), and which filters?
On Rust Data, URHEIM (local) appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on URHEIM (local) hold?
These tags are published by URHEIM (local) and read by the game's server browser: 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): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): The server runs build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to URHEIM (local)?
In Rust, F1 opens the console: type client.connect 37.48.20.204:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.