Offline NA 159.250.24.104:28034 checked 29d ago
GRIMMZONE Test Server PVE
Connect
srv = rust.server("159.250.24.104:28035")
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 61% of all ranked servers, top 78% in NA. 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 19h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 19h | 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 | Tue 29 Sep, 12:17 UTC29d ago | 1 | NaN | running | 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
- 159.250.24.104:28034
- region
- NA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 29 Sep 2026, 12:17 UTC
- hostname
- –
- first seen
- 28 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 | Rustopia.gg - US Large | NA · groups of 16+ · monthly · 134 on average | 139/200 |
| 1 | Rusty Moose |US Monthly| | NA · groups of 12+ · monthly · 113 on average | 162/200 |
| 2 | [US East] Facepunch Premium 1 | NA · groups of 8+ · monthly · 76 on average | 78/400 |
| 3 | RustLands | Monthly Large | No BP Wipe | NOOB FRIENDLY | NA · groups of 50+ · monthly · 63 on average | 57/225 |
| 4 | PICKLE DUO MONTHLY | No BP Wipe | Low Upkeep | Duo Solo | NA · groups of 20+ · monthly · 38 on average | 23/200 |
| 5 | Rusticated.com - US Premium Long | NA · groups of 16+ · monthly · 34 on average | 28/150 |
Quick answers
From the figures on this page.
Player counts
What position does GRIMMZONE Test Server PVE take in the server rankings?
Ranked #14,533 on seven-day player hours, GRIMMZONE Test Server PVE is #1,562 in North America and in the top 61% of all ranked servers.
How full does GRIMMZONE Test Server PVE run?
The current row shows GRIMMZONE Test Server PVE offline; the last response was 29 days 9 hours ago.
About the server
What Rust version does GRIMMZONE Test Server PVE run?
Version Rust network protocol 2634 and build 166165 on Windows is reported by GRIMMZONE Test Server PVE. Steam updates your game for you, but the protocol must match to join.
How reliable is GRIMMZONE Test Server PVE, and is it up?
Offline now for GRIMMZONE Test Server PVE, last seen 29 days 9 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 28 September 2026.
Where does GRIMMZONE Test Server PVE sit?
The NA tag is what GRIMMZONE Test Server PVE uses to list itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 159.250.24.104:28034 is its address.
Map and rules
Which rules apply on GRIMMZONE Test Server PVE, and what settings?
You will not find a gather rate in the string GRIMMZONE Test Server PVE. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has GRIMMZONE Test Server PVE selected?
The game generates its map: procedural, on GRIMMZONE Test Server PVE.
Wipe schedule
When does GRIMMZONE Test Server PVE wipe, and how often?
A single wipe each month, the force wipe, is all GRIMMZONE Test Server PVE does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 29 days 10 hours ago. Its tags carry a monthly wipe schedule.
What is wipe day on GRIMMZONE Test Server PVE like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold GRIMMZONE Test Server PVE, and which filters?
The Rust Data lists that GRIMMZONE Test Server PVE fits are: Rust community servers, unfiltered and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on GRIMMZONE Test Server PVE hold?
Read by the game's server browser, the tags GRIMMZONE Test Server PVE publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166165 (Build): Recorded game build: 166165; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; NA (North America): The server browser files it under North America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into GRIMMZONE Test Server PVE?
Enter client.connect 159.250.24.104:28034 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.