Online 89.179.78.59:28888 checked 9m ago
Test server autowipe
Connect
srv = rust.server("89.179.78.59:28890")
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, measured since 17 Sep. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 16:48 UTC17d 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
3000 · seed 93197
- map
- Procedural Map
- size
- 3000
- seed
- 93197
Server
srv.info()- address
- 89.179.78.59:28888
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 16:48 UTC
- hostname
- –
- first seen
- 13 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 553 on average | 394/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 234/300 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 294 on average | 43/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 293 on average | 30/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 68/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 81/200 |
Quick answers
From the figures on this page.
Player counts
How does Test server autowipe compare in the rankings?
Rank #15,344 on seven-day player hours for Test server autowipe, within the top 69% of all ranked servers.
What population does Test server autowipe carry?
Test server autowipe reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.
About the server
How well does Test server autowipe perform?
The 48-hour average is 186 server fps, with a low of 160. The entity count peaked at 48,182, covering buildings, deployables and the rest of the world. A high of 2,562 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is Test server autowipe on?
The build is Rust network protocol 2634 and build 167781 on Linux, run by Test server autowipe. Joining needs the same protocol on your game; Steam handles the update.
Is Test server autowipe up, and what does its uptime show?
Online is the state at the latest refresh for Test server autowipe. A restart about 7 days ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 13 September 2026.
Where does Test server autowipe sit?
There is no region published for Test server autowipe. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 89.179.78.59:28888.
Map and rules
Which rules apply on Test server autowipe, and what settings?
The name Test server autowipe carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, 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, Valve's anti-cheat, is enabled.
Which map has Test server autowipe selected?
The game generates the map on Test server autowipe: procedural, size 3,000, seed 93197. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does Test server autowipe wipe?
A rhythm cannot be read from the wipes of Test server autowipe 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. The world it runs now was generated 17 days 6 hours ago.
On Test server autowipe, what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain Test server autowipe?
The Rust Data lists that Test server autowipe fits are: 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.
Which meanings do the tags on Test server autowipe hold?
The game's server browser reads these tags from Test server autowipe: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. 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
How can I connect to Test server autowipe?
Enter client.connect 89.179.78.59:28888 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.