Rust Data

rustdata.spaceservers77.98.128.63:28017.ipynb

Run all rust-data · live

‹ All servers

Online 77.98.128.63:28015 checked 12m ago

W2H26

moddedoxide

Connect

srv = rust.server("77.98.128.63:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 1 # peak 1
rank #4,866 # top 22%
last wipe 5d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75122:0014:0015:0017:0018:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040022:0014:0015:0017:0018:0020: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct19 Oct23 Oct27 Oct

Top 22% 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.

usual gap1.2 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 24 Oct, 12:04 UTC3d ago 1 NaN running 1
1 Thu 22 Oct, 21:20 UTC5d ago 1 NaN 1.6 days 1
2 Tue 20 Oct, 17:40 UTC7d ago 1 held half 2.2 days 0
3 Mon 19 Oct, 23:16 UTC7d ago 1 NaN 0.8 days 0
4 Sun 18 Oct, 21:00 UTC9d ago 1 NaN 1.1 days 1
5 Sun 18 Oct, 11:55 UTC9d ago 1 NaN 0.4 days 1
6 Sat 17 Oct, 20:38 UTC10d ago 1 NaN 0.6 days 1
7 Fri 16 Oct, 14:07 UTC11d ago 1 NaN 1.3 days 1
8 Mon 12 Oct, 12:23 UTC15d ago 1 held half 4.1 days 1
9 Sun 11 Oct, 21:59 UTC15d ago 1 NaN 0.6 days 1

# 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

2000 · seed 1290386241
Map of W2H26
map
Procedural Map
size
2000
seed
1290386241
Open on RustMaps

Server

srv.info()
address
77.98.128.63:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 21:20 UTC
hostname
–
first seen
8 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average112/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average113/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average29/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average115/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average35/1000

Quick answers

From the figures on this page.

Population data

What position does W2H26 take in the server rankings?

Over the last seven days W2H26 sits at #4,866 on player hours, in the top 22% of ranked servers.

What population does W2H26 carry?

The sample now reads 1 players for W2H26, out of 100 slots. Over the last seven days it averaged 1 players and peaked at 1. Peak hour in the last 48 hours: 13:00 UTC, mean 1 players.

Server facts

How well does W2H26 perform?

Averaged over 48 hours: 229 server fps, never under 150. Entity numbers reached 17,537, and that includes buildings, deployables and the rest. A high of 1,117 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on W2H26?

The build is Rust network protocol 2635 and build 168909 on Windows, run by W2H26. Joining needs the same protocol on your game; Steam handles the update.

How reliable is W2H26, and is it up?

W2H26 reports itself online at the current refresh. A restart about 4 hours ago is what its reported uptime implies. Uptime of 32% across the last 7 full days: 54 hours of 168. Rust Data logged it first on 8 October 2026.

In which location is W2H26 hosted?

There is no region published for W2H26. Rust Data does not look up where the machine stands; it shows where a server says it is. 77.98.128.63:28015 is its address.

Map and rules

What rules and settings are recorded for W2H26?

You will not find a gather rate in the string W2H26. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has W2H26 selected?

The game generates the map on W2H26: procedural, size 2,000, seed 1290386241. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

On what schedule does W2H26 wipe?

No next wipe can be predicted for W2H26, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 5 days ago, and that is the one in play.

On W2H26, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags and filters

Where does W2H26 appear among Rust Data lists and filters?

On Rust Data, W2H26 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on W2H26 hold?

Read by the game's server browser, the tags W2H26 publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join W2H26?

Enter client.connect 77.98.128.63:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players Slot count: 100.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 71,592 players 11,819 servers online