- Players now
- 2/50 4% full
- 7-day average
- 0 peak 4
- Rank
- #4,728 ▲ 979 this week
- Wiped
- 7d 22h ago · 1 Oct, 20:30 UTC
- Next wipe
- – too few wipes seen yet
- Team limit
- 8 no published schedule
Evaluation
six readings of the figures on this page, 0 to 100 each| Population0 of 50 on average | 1 | |
|---|---|---|
| Standing#4,728 on player hours | 79 | |
| Uptime47 of the last 48 hours | 98 | |
| Performance100 server fps on average | 100 | |
| Wipe holdtoo few wipes seen | – | |
| Momentumup 979 places this week | 60 |
The score is the average of the readings that have figures. Population is the seven-day average against the slots; standing is how near the top of the rank it is; uptime the hours of the last 48 on the list; performance its server fps, 60 or more counting as full; wipe hold the share of its recent wipes that kept half their crowd; momentum its rank against a week ago, 50 for no change. The tier is the rank alone: Titanium is the top 10, Master the top 50, Diamond 150, Platinum 400, Gold 1,000, Silver 2,500.
Population
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 4 players.
Daily average and peak, UTC.
Wipe record
2 on recordNot enough wipes seen yet to tell. Every server wipes at the monthly force wipe.
- usual gap
- 1.9 days between real wipes
- wipe-day peak
- 2 players, last three wipes
The first 48 hours of its last wipes
| Date | Time | Peak | Lasted |
|---|---|---|---|
| 1 Oct FW | Thu 19:51 | 2 | running |
| 29 Sep | Tue 23:14 | 2 | 1.9 days |
Performance
48 hours: hourly readings. 30 to 90 days: a point a day, measured since 17 Sep. Low fps and a climbing entity count mean lag.
Rank history
daily · 1 is bestTop 21% of all ranked servers. Ranked on player hours over the last seven days.
Intel
![Map of [QC] WILL 2026 PVE](https://files.facepunch.com/rust/map-images/7f06e3d670a30fdbefe5464509cd937019308fac241466f2d91bafe4633bea70/proceduralmap.5000.1790886605419.289_7f06e3d670a30fdbefe5464509cd9370.jpg)
- Address
- 75.154.161.94:28015
- Region
- –
- Max players
- 50
- Group limit
- 8, the default
- Wipe schedule
- –
- Last wipe
- 1 Oct 2026, 20:30 UTC
- Hostname
- ^
- First seen
- 13 Sep 2026
Server tags
what each tag it publishes means ·mp50,ptrak,$r?,v2634,^p,gmvanilla,cs166494,ts8,^o^z| Game | gmvanilla | Game mode The mode is vanilla survival. |
mp50 | Max players Slot count: 50. | |
ts8 | Group limit The default applies: 8 to a team. | |
v2634 | Protocol Game protocol 2634 - same version required to connect. | |
cs166494 | Build Build 166494. | |
ptrak | Networking Network layer: RakNet, the game's default. | |
$r? | Region code Region code: none. | |
| Gameplay | ^p | PvE You won't fight other players - the world is what kills you. |
| Mods and access | ^o | Oxide Oxide (uMod) provides the plugin framework here. |
^z | Modded Modded category: plugins or changed settings apply. |
Flag meanings are Facepunch's.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 1[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 246 on averageUnranked219/2000
- 2[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 233 on averageUnranked289/2000
- 3Ghosty Test Servergroups of 90+ · monthly · 95 on averageUnranked0/75
- 4TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 02.10EU · groups of 30+ · biweekly · 85 on averageUnranked79/100
- 5Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 82 on averageUnranked68/250
- 6Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 78 on averageUnranked35/100
Briefing
quick answers, from the figures on this page01Where does [QC] WILL 2026 PVE sit in the rankings?
The rank for [QC] WILL 2026 PVE is #4,728 on seven-day player hours, in the top 21% of ranked servers.
02Current population on [QC] WILL 2026 PVE: how busy is it?
2 of 50 slots are filled on [QC] WILL 2026 PVE at this moment. Its seven-day average is 0 players; the peak is 4. Its busiest point in the last 48 hours was 18:00 UTC, averaging 4 players.
03The Rust version for [QC] WILL 2026 PVE: what is it?
Rust network protocol 2634 and build 166494 on Windows is what [QC] WILL 2026 PVE runs. Joining requires your game to be on the same protocol; Steam handles the update.
04Performance of [QC] WILL 2026 PVE: is it smooth?
For the last 48 hours, average server fps was 100, with a minimum of 82. 150,306 entities at peak, counting buildings and deployables. Peak memory: 5,226 MB. The lag players notice comes from low fps and rising entity counts.
05What is the host location for [QC] WILL 2026 PVE?
For [QC] WILL 2026 PVE, no region is published. Rust Server Now does not verify machine locations; it only shows where a server says it is. You reach it at 75.154.161.94:28015.
06Current online status and reliability of [QC] WILL 2026 PVE: what is the data?
Right now [QC] WILL 2026 PVE shows as online. About 6 days 5 hours ago was its last restart, based on reported uptime. It was up 98% of the time over the last 7 full days: 164 of 168 hours. Its first appearance in Rust Server Now data was on 13 September 2026.
07How should you read the tags on [QC] WILL 2026 PVE?
For the in-game browser, [QC] WILL 2026 PVE declares the following tags: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default applies: 8 to a team; v2634 (Protocol): Game protocol 2634 - same version required to connect; cs166494 (Build): Build 166494; ptrak (Networking): Network layer: RakNet, the game's default; $r? (Region code): Region code: none; ^p (PvE): You won't fight other players - the world is what kills you; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Modded category: plugins or changed settings apply. At the top of this page you also see the current players, the queue and when the world was created, all drawn from the tags.
08Where does [QC] WILL 2026 PVE show up in Rust Server Now lists and filters?
The Rust Server Now lists that carry [QC] WILL 2026 PVE are: Modded Rust servers and Rust PvE servers, ranked by population. Under these filters, it appears 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 2 weeks.
09On what timetable does [QC] WILL 2026 PVE wipe?
Too few wipes are recorded for [QC] WILL 2026 PVE to show a rhythm. Force wipe is monthly for all Rust servers, and the next is Thursday 5 November at 19:00 UTC. This world is 7 days 22 hours old.
10On wipe day, what changes for [QC] WILL 2026 PVE?
On average, 2 players was the busiest its recent wipes got. The latest wipe saw its peak 4 hours in.
11The map for [QC] WILL 2026 PVE: which one?
For [QC] WILL 2026 PVE, the map is procedural at size 5,000 with seed 753808557, generated by the game. Size and seed together determine the map, which can be viewed on RustMaps from this page.
12The rules and settings of [QC] WILL 2026 PVE: what are they?
No gather rate appears in the name [QC] WILL 2026 PVE. 8 players per group is the default and the limit here. pve is the game mode, no combat between players. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running. The VAC anti-cheat from Valve is on.
13To join [QC] WILL 2026 PVE, what must you do?
To connect, open Rust, press F1, and enter client.connect 75.154.161.94:28015. You can also click Launch Rust here to open the game via Steam and join.