Rust Server TrendsSeismic network · station log
Recording Stations11,835 Players94,909 Active3,850 Wipes · 3 h528 48 h

Station XX-15494 · no signal

arukumasaba

Offline 45.140.128.97:10100 checked 36d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,494
top 67%
Last wipe
49d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15494 · 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 17 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
15k10k15k20k20 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 151 on average
78/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
131/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
42/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 91 on average
135/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
347/ 350
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on arukumasaba?

arukumasaba runs a procedural map of size 3,500 with seed 6738, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on arukumasaba?

You will find no gather rate in the name of arukumasaba. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of 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. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on arukumasaba right now?

A reading taken now finds arukumasaba offline; the most recent activity was 36 days 18 hours ago.

How does arukumasaba rank against other Rust servers?

The last seven days of player hours place arukumasaba at #15,494, in the top 67% of all ranked servers.

Operator and location

How reliably does arukumasaba stay online?

No contact with arukumasaba right now, and the last recorded contact was 36 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does arukumasaba run from?

No region is published by arukumasaba. 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 45.140.128.97:10100.

What build of Rust does arukumasaba use?

arukumasaba is running Rust network protocol 2633 and build 165217 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

How often does arukumasaba wipe, and on which days?

On record so far are too few of arukumasaba's wipes to tell its rhythm. 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 49 days 4 hours.

Lists and tags

What do the server tags on arukumasaba mean?

The game's server browser reads the tags arukumasaba publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; 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. 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 arukumasaba appear?

The Rust Server Trends lists that take in arukumasaba are: 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.

How to join

How do you connect to arukumasaba?

You can connect by pressing F1 in Rust and typing client.connect 45.140.128.97:10100 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?,v2633,gmvanilla,cs165217,ts8,^o^z

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp50
Max players 50 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build The game build is 165217.
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.