RUST METRICSFlight deck · live data
Data live Servers11,894 Players99,159 Populated3,939 Fresh wipes 3 h396 Scan5 min
‹ All servers51.38.13.133:26025
Offline Full Queue Fresh wipe Wipe due No query

RAID1

Offline 51.38.13.133:26025 checked 23d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,980top 71%
Last wipe23d agono schedule published
Next wipe–too few wipes 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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k5 Oct7 Oct8 Oct10 Oct11 Oct13 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak14players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 17:15 UTC23d ago 14 – running 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.

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

What should you expect from wipe day on RAID1?

The busiest point of its recent wipes drew 14 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does RAID1 follow?

Its rhythm cannot be told from the wipes of RAID1 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 23 days 23 hours ago the current world was made.

Lists and filters

Which tags does RAID1 carry, and what do they mean?

Tags published by RAID1, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does RAID1 appear in Rust Metrics lists and filters?

On Rust Metrics, RAID1 sits in these lists: 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.

Population

What position does RAID1 hold among Rust servers?

Ranking for RAID1: #15,980 on seven-day player hours, top 71% of all ranked servers.

How full does RAID1 get?

Reading for RAID1: offline at this moment; last seen 23 days 6 hours ago.

Server details

Where does RAID1 sit?

Reading: location. RAID1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 51.38.13.133:26025.

What Rust version is RAID1 on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by RAID1. To get in, your game needs the same protocol; Steam applies the update.

Is RAID1 up, and how often does it stay up?

RAID1 reports offline. The last reading came 23 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 5 October 2026.

Map and rules

What rules does RAID1 enforce, and what are its settings?

No gather rate appears in the name: RAID1. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on RAID1?

Size 2,500 and seed 3486489: the game generates the procedural map on RAID1 from them. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Custom Map.

Connection

What do you do to join RAID1?

Check: join. Open Rust, press F1, then enter client.connect 51.38.13.133:26025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmvanilla,cs166652,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.