Rust Server TrendsSeismic network · station log
Recording Stations11,795 Players71,386 Active3,684 Wipes · 3 h118 48 h

Station XX-15348 · no signal

UMAISAKEUMAISAKE

Offline 162.43.26.65:28015 checked 5d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,348
top 69%
Last wipe
9d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15348 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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 21 Sep. 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
15k10k15k20k21 Sep28 Sep6 Oct13 Oct21 Oct28 Oct

Top 69% 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
0.9 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

Mon 19 OctSun 18 OctSat 17 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
Mon 19 Oct, 02:12 UTC9d ago M0.0steady 1 – running 1
Sun 18 Oct, 13:17 UTC10d ago M0.0rising 1 – 0.5 days 0
Sat 17 Oct, 10:18 UTC11d ago M0.0steady 1 – 1.1 days 1
Fri 16 Oct, 13:40 UTC12d ago M0.0steady 1 – 0.9 days 1
Sun 11 Oct, 22:45 UTC16d ago M0.0rising 1 held half 4.6 days 0
Sat 10 Oct, 15:34 UTC18d ago M0.0steady 1 – 1.3 days 1
Fri 9 Oct, 16:06 UTC19d ago M0.0steady 1 – 1 days 1
Fri 9 Oct, 02:57 UTC19d ago M0.0rising 1 – 0.5 days 0
Thu 8 Oct, 13:08 UTC20d ago M0.0rising 1 – 0.6 days 0
Mon 5 Oct, 08:49 UTC23d ago M0.0rising 1 – 3.2 days 0

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
106/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
123/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 91 on average
93/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
25/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
26/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on UMAISAKEUMAISAKE?

UMAISAKEUMAISAKE runs a procedural map of size 5,000 with seed 753808557, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on UMAISAKEUMAISAKE?

You will find no gather rate in the name of UMAISAKEUMAISAKE. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

How many players are recorded on UMAISAKEUMAISAKE right now?

UMAISAKEUMAISAKE is not responding at this moment and is offline, last seen 5 days 8 hours ago. Averaged across the last seven days, the population was 0 players.

How does UMAISAKEUMAISAKE rank against other Rust servers?

The last seven days of player hours place UMAISAKEUMAISAKE at #15,348, in the top 69% of all ranked servers.

Server details

How reliably does UMAISAKEUMAISAKE stay online?

UMAISAKEUMAISAKE is down at the moment; the last recorded contact was 5 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 1, or 1% of the time. On 21 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does UMAISAKEUMAISAKE run from?

No region is published by UMAISAKEUMAISAKE. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 162.43.26.65:28015.

What build of Rust does UMAISAKEUMAISAKE use?

Rust network protocol 2635 and build 168909 on Linux is what UMAISAKEUMAISAKE runs. 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 UMAISAKEUMAISAKE?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.

How often does UMAISAKEUMAISAKE wipe, and on which days?

No next wipe can be predicted for UMAISAKEUMAISAKE, 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. It has run its current world for 9 days 19 hours.

Server tags

What do the server tags on UMAISAKEUMAISAKE mean?

These are the tags UMAISAKEUMAISAKE publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does UMAISAKEUMAISAKE appear?

You will find UMAISAKEUMAISAKE on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Join the server

What steps get you onto UMAISAKEUMAISAKE?

You can connect by pressing F1 in Rust and typing client.connect 162.43.26.65:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players 50 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.