Offline 23.234.82.43:28015 checked 11d ago
WipeHype TEST (local)
Connect
srv = rust.server("23.234.82.43: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 70% of all ranked servers, and #627 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 18:06 UTC, in 1d 19h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 1d 19h | Sat 31 Oct, 18:06 UTC | wipe |
| 1 | 6d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 15d 19h | Sat 14 Nov, 18:06 UTC | wipe |
| 3 | 29d 19h | Sat 28 Nov, 18:06 UTC | wipe |
| 4 | 34d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 43d 19h | Sat 12 Dec, 18:06 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 9 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 18:06 UTC12d ago | 1 | NaN | running | 0 |
| 1 | Sat 17 Oct, 05:37 UTC12d ago | 1 | NaN | 0.5 days | 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
- 23.234.82.43:28015
- region
- –
- max players
- 10
- group limit
- quad
- wipe schedule
- biweekly
- last wipe
- 17 Oct 2026, 18:06 UTC
- hostname
- –
- first seen
- 17 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 | PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVP | NA · groups of 8+ · 5 on average | 1/10 |
| 1 | MINICOPTER / HELICOPTER TRAINING | groups of 8+ · 5 on average | 3/100 |
| 2 | ･RUST KILL･XXX|KILL $ CASH|FARM|SHOP|TP|HOME|KITS|PVPVEX10X | groups of 10+ · weekly · 5 on average | 4/100 |
| 3 | [EU] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 | EU · no group limit · 4 on average | 14/100 |
| 4 | [US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 | NA · no group limit · 2 on average | 3/100 |
| 5 | PVP Arena | Aimtrain | groups of 8+ · 1 on average | 0/40 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does WipeHype TEST (local) rank?
Rank #15,255 on seven-day player hours for WipeHype TEST (local), within the top 70% of all ranked servers. The quad group places it at #627.
What population does WipeHype TEST (local) carry?
Offline now for WipeHype TEST (local), with the last sample 11 days 3 hours ago.
About the server
Which Rust version is WipeHype TEST (local) on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by WipeHype TEST (local). The protocol has to match before you can join, and Steam does the updating.
How reliable is WipeHype TEST (local), and is it up?
Offline now for WipeHype TEST (local), last seen 11 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 17 October 2026.
Which location does WipeHype TEST (local) run from?
For WipeHype TEST (local), no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 23.234.82.43:28015.
Settings and map
What rules and settings are recorded for WipeHype TEST (local)?
The name WipeHype TEST (local) carries no gather rate. The group limit is 4 players, the quad setting. combat training is the game mode here, and loot handed out for aim and PvP practice. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has WipeHype TEST (local) loaded?
WipeHype TEST (local) runs a procedural map, which the game generates.
Wipe schedule
On what schedule does WipeHype TEST (local) wipe?
Too few wipes are on record for WipeHype TEST (local) to confirm its schedule, so the tag drives the prediction. On Saturday 31 October at 18:06 UTC the next wipe is due. This world was created 12 days 4 hours ago. The tags list a two-weekly wipe cycle.
On WipeHype TEST (local), what happens on wipe day?
The average peak over recent wipes is 1 players. 9 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain WipeHype TEST (local)?
The Rust Data lists that WipeHype TEST (local) fits are: Modded Rust servers and Rust aim training servers. It appears under these filters on the server list: Type: Modded; Server tag: Biweekly ^b, Combat training ^d, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
How should you read the server tags on WipeHype TEST (local)?
The game's server browser reads these tags from WipeHype TEST (local): gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts4 (Group limit): The team cap is 4; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^d (Combat training): Training server: practise aim and PvP, loot supplied; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Join steps
What is the way to join WipeHype TEST (local)?
In Rust, F1 opens the console: type client.connect 23.234.82.43:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.