Offline 159.69.176.218:28915 checked 9d ago
PWC local test
Connect
srv = rust.server("159.69.176.218:28917")
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. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 05:59 UTC9d ago | 0 | NaN | running | 0 |
| 1 | Wed 14 Oct, 11:22 UTC15d ago | 0 | NaN | 5.8 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
- 159.69.176.218:28915
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 05:59 UTC
- hostname
- –
- first seen
- 14 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 184/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 86/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 28/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 28/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 265/700 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does PWC local test rank?
Over the last seven days PWC local test sits at #15,353 on player hours, in the top 70% of ranked servers.
How full does PWC local test run?
The current row shows PWC local test offline; the last response was 9 days 7 hours ago.
Server data
What is the Rust version on PWC local test?
Rust network protocol 2634 and build 167584 on Windows is what PWC local test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is PWC local test, and is it online now?
Offline now for PWC local test, last seen 9 days 7 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 14 October 2026.
In which location is PWC local test hosted?
For PWC local test, 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 159.69.176.218:28915.
Rules, settings, map
Which settings and rules does PWC local test run?
No gather rate appears in the name: PWC local test. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has PWC local test selected?
PWC local test runs a procedural map, which the game generates.
Wipe data
When does PWC local test wipe, and on what schedule?
Too few wipes are on record for PWC local test to reveal its rhythm. 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 9 days 7 hours ago.
On PWC local test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags, lists
Which Rust Data filters and lists contain PWC local test?
These Rust Data lists include PWC local test: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on PWC local test?
These tags are published by PWC local test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167584 (Build): Recorded game build: 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into PWC local test?
The manual route: launch Rust, F1, then client.connect 159.69.176.218:28915. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.