W2H26
Offline 77.98.128.63:28015 checked 4h ago
Server instruments
last reading Wed 00:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 150 · below 20 is lag, below 10 is badEntities
48 h range 11,799–18,529 · memory 914 MBUptime
1 h 12 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 12 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 22% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 12:04 UTC3d ago | 1 | – | running | 1 |
| Thu 22 Oct, 21:20 UTC5d ago | 1 | – | 1.6 days | 1 |
| Tue 20 Oct, 17:40 UTC7d ago | 1 | held half | 2.2 days | 0 |
| Mon 19 Oct, 23:16 UTC8d ago | 1 | – | 0.8 days | 0 |
| Sun 18 Oct, 21:00 UTC9d ago | 1 | – | 1.1 days | 1 |
| Sun 18 Oct, 11:55 UTC9d ago | 1 | – | 0.4 days | 1 |
| Sat 17 Oct, 20:38 UTC10d ago | 1 | – | 0.6 days | 1 |
| Fri 16 Oct, 14:07 UTC11d ago | 1 | – | 1.3 days | 1 |
| Mon 12 Oct, 12:23 UTC15d ago | 1 | held half | 4.1 days | 1 |
| Sun 11 Oct, 21:59 UTC16d ago | 1 | – | 0.6 days | 1 |
| Sun 11 Oct, 15:39 UTC16d ago | 1 | – | 0.3 days | 0 |
| Thu 8 Oct, 20:52 UTC19d ago | 0 | – | 2.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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 44/500
- 125/100
- 53/225
- 22/700
- 4/200
- 6/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on W2H26?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
How often does W2H26 wipe, and when?
There is no next wipe to predict: W2H26 wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 5 days 6 hours ago the current world was made.
Tag meanings
Which tags does W2H26 carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from W2H26. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does W2H26 appear in Rust Metrics lists and filters?
On Rust Metrics, W2H26 sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Player count
Where does W2H26 sit in the rankings?
Player hours over seven days put W2H26 at #4,876, in the top 22% of all ranked servers.
How full does W2H26 get?
W2H26 is not responding; status offline, last seen 4 hours ago. Check: players over seven days. Average 1, peak 1. Average at the busiest hour was 1 players, at 13:00 UTC over the last 48 hours.
Server details
Where does W2H26 sit?
No region comes from W2H26. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 77.98.128.63:28015.
What Rust version is W2H26 on?
Reading: W2H26, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for W2H26?
Check: fps. Average 232 server fps over the last 48 hours, low of 150. Within range. Reading: 18,529 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 1,176 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is W2H26 up, and how often does it stay up?
W2H26 reports offline. The last reading came 4 hours ago. By its reported uptime, the last restart was roughly 1 hours ago. Uptime for the last 7 full days: 58 of 168 hours, or 35%. The first sighting on Rust Metrics was 8 October 2026.
Rules and settings
What rules does W2H26 enforce, and what are its settings?
Reading the name gives no gather rate for W2H26. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is W2H26 on?
Size 2,000 and seed 1290386241: the game generates the procedural map on W2H26 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How can you get onto W2H26?
To join: start Rust, press F1 and type client.connect 77.98.128.63:28015. Or press Launch Rust here and Steam opens the game and connects you.