Offline 85.234.84.19:28515 checked 18d ago
Rust WakeExp 7 (private insecure test)
Connect
srv = rust.server("85.234.84.19:28516")
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 best
Top 72% 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 0, 19 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 14:47 UTC20d 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
- 85.234.84.19:28515
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 14:47 UTC
- hostname
- –
- first seen
- 9 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 · 549 on average | 147/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 125/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 284 on average | 18/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 13/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 38/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Rust WakeExp 7 (private insecure test) rank?
Rank #15,814 on seven-day player hours for Rust WakeExp 7 (private insecure test), within the top 72% of all ranked servers.
How full does Rust WakeExp 7 (private insecure test) run?
Rust WakeExp 7 (private insecure test) returns no live count at this refresh, having last been seen 18 days 23 hours ago.
Server data
What is the Rust version on Rust WakeExp 7 (private insecure test)?
Rust network protocol 2634 and build 166652 on Linux is what Rust WakeExp 7 (private insecure test) runs. Joining needs the same protocol on your game; Steam handles the update.
Is Rust WakeExp 7 (private insecure test) up, and what does its uptime show?
Rust WakeExp 7 (private insecure test) is offline at this refresh; the last response came 18 days 23 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 9 October 2026.
Where does Rust WakeExp 7 (private insecure test) sit?
There is no region published for Rust WakeExp 7 (private insecure test). 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 85.234.84.19:28515.
Map and rules
Which rules apply on Rust WakeExp 7 (private insecure test), and what settings?
You will not find a gather rate in the string Rust WakeExp 7 (private insecure test). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC is not running; Valve's anti-cheat is off.
Which map has Rust WakeExp 7 (private insecure test) selected?
A procedural map runs on Rust WakeExp 7 (private insecure test), generated by the game.
Wipe schedule
When does Rust WakeExp 7 (private insecure test) wipe, and how often?
A rhythm cannot be read from the wipes of Rust WakeExp 7 (private insecure test) on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 20 days 14 hours ago.
What is wipe day on Rust WakeExp 7 (private insecure test) like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 19 hours in.
Tags and filters
Which lists on Rust Data hold Rust WakeExp 7 (private insecure test), and which filters?
These Rust Data lists include Rust WakeExp 7 (private insecure test): Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Rust WakeExp 7 (private insecure test)?
The game's server browser reads these tags from Rust WakeExp 7 (private insecure test): gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Rust WakeExp 7 (private insecure test)?
Enter client.connect 85.234.84.19:28515 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.