RUST METRICSFlight deck · live data
Data live Servers11,694 Players35,972 Populated2,914 Fresh wipes 3 h94 Scan5 min
‹ All servers45.140.128.97:10100
Offline Full Queue Fresh wipe Wipe due No query

arukumasaba

Offline 45.140.128.97:10100 checked 36d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,494top 67%
Last wipe48d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

When does arukumasaba wipe?

Its rhythm cannot be told from the wipes of arukumasaba on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 48 days 10 hours ago.

Tag meanings

How should you read the tags on arukumasaba?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server from arukumasaba. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does arukumasaba appear in Rust Metrics lists and filters?

These Rust Metrics lists carry arukumasaba: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does arukumasaba sit in the rankings?

Player hours over seven days put arukumasaba at #15,494, in the top 67% of all ranked servers.

What player count does arukumasaba carry?

Reading for arukumasaba: offline at this moment; last seen 36 days ago.

Server details

Where does arukumasaba sit?

No region tag on arukumasaba. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 45.140.128.97:10100.

What Rust version is arukumasaba on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by arukumasaba. Matching protocol is required to join. Let Steam update your game.

What is the uptime on arukumasaba, and is it online?

Check: connection. arukumasaba is offline at this moment. Last contact was 36 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

How is arukumasaba configured, and what rules are in force?

No gather rate appears in the name: arukumasaba. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on arukumasaba?

From seed 6738, the game generates the procedural map on arukumasaba. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How can you get onto arukumasaba?

To join: start Rust, press F1 and type client.connect 45.140.128.97:10100. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs165217,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.