W2H26
Offline 77.98.128.63:28015 checked 5h ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 22% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on W2H26?
At their busiest, its recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 100% of its recent wipes.
What is the wipe schedule on W2H26?
There is no next wipe to predict on W2H26, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 5 days 8 hours ago the server made the world it is on now.
Population
How busy is W2H26?
Last seen 5 hours ago, W2H26 is offline at the moment. The average across the last seven days is 1 players; the peak reached 1. Look at 13:00 UTC for the last 48 hours: that hour averaged 1 players.
How does W2H26 rank against other Rust servers?
Ranked #4,884 on seven-day player hours, W2H26 is in the top 22% of all ranked servers.
Rules and settings
Which map does W2H26 run?
A procedural map of size 2,000 with seed 1290386241, generated by the game, runs on W2H26. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on W2H26?
A gather rate is not given in the name W2H26. Groups can contain up to 8 players, the default in the game. survival is the game mode, gather, build and raid in the standard game. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does W2H26 run?
Rust network protocol 2635 and build 168909 is the build W2H26 runs, on Windows. To join, your game must match the protocol; Steam handles the update.
Is W2H26 online, and how reliable is it?
W2H26 is down just now; the last sighting was 5 hours ago. The uptime it reports puts the last restart at about 1 hours ago. It was up 58 of 168 hours across the last 7 full days, or 35% of the time. The first record of it on Rust Heatmap is 8 October 2026.
Where is W2H26 located?
A region is not published for W2H26. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 77.98.128.63:28015.
Does W2H26 run smoothly?
Average server fps over the last 48 hours was 232; it never dropped below 150. The world held as many as 18,529 entities, buildings and deployables included. At its peak it held 1,176 MB of memory. What players call lag is low fps together with a growing entity count.
Tags
Which Rust Heatmap lists and filters include W2H26?
Modded Rust servers, by live population are the Rust Heatmap lists that W2H26 fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
What do the server tags on W2H26 mean?
These are the tags W2H26 publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Listed as Modded, since settings or plugins change the game. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join W2H26?
Enter client.connect 77.98.128.63:28015 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.