Online NA 38.97.61.172:33000 checked 30m ago
Weekend Warriors 3 HC PVE NPCs Events Raids
Connect
srv = rust.server("38.97.61.172:33001")
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 best
Top 19% of all ranked servers, top 38% in NA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 17h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 18h | Thu 12 Nov, 19:59 UTC | wipe |
| 2 | 27d 18h | Thu 26 Nov, 19:59 UTC | wipe |
| 3 | 34d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 18h | Thu 10 Dec, 19:59 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 3 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 19:59 UTC14d ago | 4 | NaN | running | 0 |
| 1 | Thu 1 Oct, 18:42 UTC FW28d ago | 5 | halved by day 7 | 14.1 days | 0 |
| 2 | Thu 17 Sep, 18:13 UTC42d ago | 5 | halved by day 4 | 14 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
4338 · seed 0- map
- Procedural Map
- size
- 4338
- seed
- –
Server
srv.info()- address
- 38.97.61.172:33000
- region
- NA
- max players
- 60
- group limit
- teams off
- wipe schedule
- biweekly
- last wipe
- 15 Oct 2026, 19:59 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | RustNK - Custom Hardcore PvE, NPCs, Events & Quests | NA · no group limit · biweekly · 5 on average | 25/50 |
| 1 | HZ Casual Rust | 1X Hybrid PvP/PvE | Chill/Noob Friendly | NA · no group limit · 1x · biweekly · 2 on average | 4/50 |
| 2 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 250 on average | 294/2000 |
| 3 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 104 on average | 100/200 |
| 4 | Orange Dream | Cozy PvE/RP | No KOS | NA · groups of 8+ · biweekly · 34 on average | 99/200 |
| 5 | LuffyRust Texas USA - 10xPvE|NoBP|Kits|Skins|Backpacks|Purge No | NA · groups of 12+ · biweekly · 15 on average | 20/40 |
Quick answers
From the figures on this page.
Population
How does Weekend Warriors 3 HC PVE NPCs Events Raids compare in the rankings?
On seven-day player hours Weekend Warriors 3 HC PVE NPCs Events Raids is #4,239 overall and #703 in North America, inside the top 19% of all ranked servers.
How full does Weekend Warriors 3 HC PVE NPCs Events Raids run?
Weekend Warriors 3 HC PVE NPCs Events Raids reports 1 players at this refresh, with 60 slots configured. Over the last seven days it averaged 0 players and peaked at 4. The 48-hour sample puts the busiest hour at 23:00 UTC, averaging 1 players.
Server facts
How well does Weekend Warriors 3 HC PVE NPCs Events Raids perform?
The 48-hour average is 40 server fps, with a low of 40. Buildings, deployables and all else in the world took the count as high as 128,468 entities. The memory field tops out at 4,610 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Weekend Warriors 3 HC PVE NPCs Events Raids?
Version Rust network protocol 2635 and build 168909 on Linux is reported by Weekend Warriors 3 HC PVE NPCs Events Raids. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Weekend Warriors 3 HC PVE NPCs Events Raids, and is it up?
Weekend Warriors 3 HC PVE NPCs Events Raids reports itself online at the current refresh. A restart about 15 hours ago is what its reported uptime implies. Uptime of 85% across the last 7 full days: 143 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does Weekend Warriors 3 HC PVE NPCs Events Raids run from?
With its NA tag, Weekend Warriors 3 HC PVE NPCs Events Raids lists itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 38.97.61.172:33000.
Rules, settings, map
What rules and settings are recorded for Weekend Warriors 3 HC PVE NPCs Events Raids?
No gather rate appears in the name: Weekend Warriors 3 HC PVE NPCs Events Raids. The field for group size is empty. Game mode hardcore, with this note: Facepunch's most punishing mode. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is not running; Valve's anti-cheat is off.
Which map has Weekend Warriors 3 HC PVE NPCs Events Raids loaded?
A procedural map of size 4,338 runs on Weekend Warriors 3 HC PVE NPCs Events Raids, generated by the game.
Wipe schedule
When does Weekend Warriors 3 HC PVE NPCs Events Raids wipe, and how often?
The prediction follows the tag, because Weekend Warriors 3 HC PVE NPCs Events Raids's wipes on record are too few to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 14 days 5 hours ago. The tags list a two-weekly wipe cycle.
What is wipe day on Weekend Warriors 3 HC PVE NPCs Events Raids like?
Across recent wipes the busiest point averaged 5 players. 3 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 5.5.
Tags and filters
Where does Weekend Warriors 3 HC PVE NPCs Events Raids appear among Rust Data lists and filters?
The Rust Data lists that Weekend Warriors 3 HC PVE NPCs Events Raids fits are: Modded Rust servers, Rust PvE servers and North America Rust servers. It appears under these filters on the server list: Region: North America; Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, Hardcore ^h, PvE ^p, Modded ^z and Oxide ^o; Wipe schedule: Every two weeks.
How should you read the server tags on Weekend Warriors 3 HC PVE NPCs Events Raids?
These tags are published by Weekend Warriors 3 HC PVE NPCs Events Raids and read by the game's server browser: gmhardcore (Game mode): Hardcore ruleset, the harsher one; mp60 (Max players): Slot count: 60; ts0 (Group limit): Teams are disabled; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^h (Hardcore): Hardcore mode from Facepunch: harsher survival, fewer helpers; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it sits under North America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Weekend Warriors 3 HC PVE NPCs Events Raids?
In Rust, F1 opens the console: type client.connect 38.97.61.172:33000. Launch Rust on this page does the same by opening the game through Steam and connecting. https://weekendwarrior.murc.site/ is the website recorded for it.