Online 75.154.161.94:28015 checked 11m ago
[QC] WILL 2026 PVE
Connect
srv = rust.server("75.154.161.94:28016")
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 26% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 4 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 19:17 UTC6h ago | NaN | NaN | running | 0 |
| 1 | Thu 1 Oct, 19:51 UTC FW26d ago | 2 | halved by day 11 | 26 days | 0 |
| 2 | Tue 29 Sep, 23:14 UTC28d ago | 2 | NaN | 1.9 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
5000 · seed 753808557![Map of [QC] WILL 2026 PVE](https://files.facepunch.com/rust/map-images/3f337b0c987e73f1eb63741f868f0afcaf696f755689c8b143e99491899d1460/5000_25.5000.1785858743322.289_3f337b0c987e73f1eb63741f868f0afc.jpg)
- map
- Custom Map
- size
- 5000
- seed
- 753808557
Server
srv.info()- address
- 75.154.161.94:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 20:18 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 244 on average | 308/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 235 on average | 129/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 97 on average | 138/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 60 on average | 29/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 53 on average | 14/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 52 on average | 48/250 |
Quick answers
From the figures on this page.
Player counts
How does [QC] WILL 2026 PVE compare in the rankings?
Player hours over seven days put [QC] WILL 2026 PVE at #5,828, in the top 26% of the ranked set.
How many players does [QC] WILL 2026 PVE hold at once?
Current row: 0 players on [QC] WILL 2026 PVE, against 50 slots. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 23:00 UTC, averaging 1 players.
Server data
What does performance look like on [QC] WILL 2026 PVE?
Averaged over 48 hours: 97 server fps, never under 16. The entity count peaked at 152,002, covering buildings, deployables and the rest of the world. Memory peaked at 5,360 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does [QC] WILL 2026 PVE run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [QC] WILL 2026 PVE. The protocol has to match before you can join, and Steam does the updating.
How reliable is [QC] WILL 2026 PVE, and is it up?
[QC] WILL 2026 PVE reports itself online at the current refresh. A restart about 11 minutes ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is [QC] WILL 2026 PVE hosted?
No region is published by [QC] WILL 2026 PVE. 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 75.154.161.94:28015.
Map and rules
Which rules apply on [QC] WILL 2026 PVE, and what settings?
The name [QC] WILL 2026 PVE carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as pve, player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has [QC] WILL 2026 PVE selected?
Size 5,000, seed 753808557: the procedural map on [QC] WILL 2026 PVE, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipe schedule
When does [QC] WILL 2026 PVE wipe, and on what schedule?
No next wipe can be predicted for [QC] WILL 2026 PVE, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 5 hours ago, and that is the one in play.
What is wipe day on [QC] WILL 2026 PVE like?
Across recent wipes the busiest point averaged 2 players. 4 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 11.
Lists and tags
Where does [QC] WILL 2026 PVE appear among Rust Data lists and filters?
The Rust Data lists that [QC] WILL 2026 PVE fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Which meanings do the tags on [QC] WILL 2026 PVE hold?
These tags are published by [QC] WILL 2026 PVE and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; 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; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.
Connecting
What is the way to join [QC] WILL 2026 PVE?
Enter client.connect 75.154.161.94:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.