Offline 178.235.12.18:28015 checked 17d ago
wag
Connect
srv = rust.server("178.235.12.18: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 61% 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 7d 10h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 10h | 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 08:06 UTC26d ago | 1 | NaN | running | 1 |
| 1 | Fri 25 Sep, 18:40 UTC33d ago | 1 | NaN | 7.6 days | 1 |
# 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
- 178.235.12.18:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 3 Oct 2026, 08:06 UTC
- hostname
- –
- first seen
- 19 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 47/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 20/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 79 on average | 179/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 71 on average | 78/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 66 on average | 10/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 64 on average | 166/1000 |
Quick answers
From the figures on this page.
Player counts
What position does wag take in the server rankings?
Over the last seven days wag sits at #13,581 on player hours, in the top 61% of ranked servers.
What population does wag carry?
wag returns no live count at this refresh, having last been seen 17 days 18 hours ago.
About the server
What is the Rust version on wag?
The build is Rust network protocol 2634 and build 166652 on Windows, run by wag. The protocol has to match before you can join, and Steam does the updating.
Is wag up, and what does its uptime show?
wag is offline at this refresh; the last response came 17 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 19 September 2026.
Where does wag sit?
For wag, 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 178.235.12.18:28015.
Settings and map
What rules and settings are recorded for wag?
You will not find a gather rate in the string wag. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has wag selected?
The game generates its map: procedural, on wag.
Wipe data
When does wag wipe, and how often?
Once a month wag 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 ago. Its tags carry a monthly wipe schedule.
What is wipe day on wag like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain wag?
These Rust Data lists include wag: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on wag hold?
Read by the game's server browser, the tags wag publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 wag?
Enter client.connect 178.235.12.18:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.