Offline 151.240.92.7:28015 checked 16d ago
Hotwire Test Renamed
Connect
srv = rust.server("151.240.92.7: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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 3 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:11 UTC FW26d ago | 0 | 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
- 151.240.92.7:28015
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:11 UTC
- hostname
- –
- first seen
- 30 Sep 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 · 163 on average | 171/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 141/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 33/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 145/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 46/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Hotwire Test Renamed rank?
Rank #15,850 on seven-day player hours for Hotwire Test Renamed, within the top 72% of all ranked servers.
What population does Hotwire Test Renamed carry?
Offline now for Hotwire Test Renamed, with the last sample 16 days 15 hours ago.
About the server
What is the Rust version on Hotwire Test Renamed?
The build is Rust network protocol 2634 and build 167398 on Windows, run by Hotwire Test Renamed. The protocol has to match before you can join, and Steam does the updating.
How reliable is Hotwire Test Renamed, and is it online now?
Hotwire Test Renamed is offline at this refresh; the last response came 16 days 15 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 30 September 2026.
Which location does Hotwire Test Renamed run from?
For Hotwire Test Renamed, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 151.240.92.7:28015.
Rules, settings, map
Which rules apply on Hotwire Test Renamed, and what settings?
No gather rate appears in the name: Hotwire Test Renamed. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on Hotwire Test Renamed?
The game generates its map: procedural, on Hotwire Test Renamed.
Wipes and dates
When does Hotwire Test Renamed wipe, and how often?
Once a month Hotwire Test Renamed wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 26 days 2 hours ago.
What is wipe day on Hotwire Test Renamed like?
Recent wipes averaged 0 players at their peak. 3 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain Hotwire Test Renamed?
These Rust Data lists include Hotwire Test Renamed: 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.
Which meanings do the tags on Hotwire Test Renamed hold?
The game's server browser reads these tags from Hotwire Test Renamed: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into Hotwire Test Renamed?
The manual route: launch Rust, F1, then client.connect 151.240.92.7:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.