Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h23 48 h

Station XX-4976 · no signal

W2H26

Offline 77.98.128.63:28015 checked 19h ago

moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 1
Rank
#4,976
top 22%
Last wipe
5d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-4976 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Tue 19:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75113:0015:0017:0020:0022:0000:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040013:0015:0017:0020:0022:0000:00

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct20 Oct24 Oct28 Oct

Top 22% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
1.2 daysbetween real wipes
on rhythm
25%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 24 OctThu 22 OctTue 20 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 24 Oct, 12:04 UTC4d ago M0.0steady 1 – running 1
Thu 22 Oct, 21:20 UTC5d ago M0.0steady 1 – 1.6 days 1
Tue 20 Oct, 17:40 UTC8d ago M0.0rising 1 held half 2.2 days 0
Mon 19 Oct, 23:16 UTC8d ago M0.0rising 1 – 0.8 days 0
Sun 18 Oct, 21:00 UTC9d ago M0.0steady 1 – 1.1 days 1
Sun 18 Oct, 11:55 UTC10d ago M0.0steady 1 – 0.4 days 1
Sat 17 Oct, 20:38 UTC10d ago M0.0steady 1 – 0.6 days 1
Fri 16 Oct, 14:07 UTC12d ago M0.0steady 1 – 1.3 days 1
Mon 12 Oct, 12:23 UTC16d ago M0.0steady 1 held half 4.1 days 1
Sun 11 Oct, 21:59 UTC16d ago M0.0steady 1 – 0.6 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
205/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 127 on average
121/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 90 on average
126/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
19/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
50/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on W2H26?

Generated by the game, the map on W2H26 is procedural, size 2,000 with seed 1290386241. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on W2H26?

The name of W2H26 gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on W2H26?

A reading taken now finds W2H26 offline; the most recent activity was 19 hours ago. The seven-day average is 1 players, with a peak of 1. The last 48 hours show their highest activity at 13:00 UTC, averaging 1 players.

How does W2H26 rank against other Rust servers?

Over the last seven days, W2H26 recorded enough player hours to reach #4,976 worldwide, placing it in the top 22% of all ranked servers.

Server details

How reliably does W2H26 stay online?

As recorded now, W2H26 is not reachable, the last contact having been 19 hours ago. Its reported uptime points to a restart about 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 58, or 35% of the time. 8 October 2026 is when Rust Server Trends first recorded it.

Does W2H26 hold a steady tick rate?

Across the last 48 hours it averaged 232 server fps, with a floor of 150. The world held up to 18,529 entities at its peak, buildings and deployables included. Its highest memory use was 1,176 MB. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is W2H26 hosted?

Nothing about a region comes from W2H26. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 77.98.128.63:28015.

What build of Rust does W2H26 use?

On Windows, W2H26 runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on W2H26?

The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

On what timetable does W2H26 run its wipes?

No next wipe can be predicted for W2H26, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 5 days 22 hours is how long the current world has been running.

Tags

What do the server tags on W2H26 mean?

Tags published by W2H26 and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does W2H26 appear?

You will find W2H26 on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Join the server

What steps get you onto W2H26?

To join, enter client.connect 77.98.128.63:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players 100 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.