RUST METRICSFlight deck · live data
Data live Servers11,867 Players96,005 Populated3,901 Fresh wipes 3 h390 Scan5 min
‹ All servers94.183.203.31:35100
Offline Full Queue Fresh wipe Wipe due No query

2_X2 test

Offline 94.183.203.31:35100 checked 32d ago

2x moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 162 325 488 650 PAX 0 /650

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#16,897top 72%
Last wipe35d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep25 Sep27 Sep29 Sep1 Oct3 Oct

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

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 24 Sep, 01:12 UTC35d ago – – running 0

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

Wipe timing

What wipe timing does 2_X2 test follow?

The rhythm of 2_X2 test's wipes cannot be told yet: too few are on record. 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 35 days 15 hours ago.

Tag meanings

Which tags does 2_X2 test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp650 (Max players): The server holds 650 slots; ts100 (Group limit): You may team up with at most 100; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from 2_X2 test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does 2_X2 test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 2_X2 test: 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

Population

What position does 2_X2 test hold among Rust servers?

Ranking for 2_X2 test: #16,897 on seven-day player hours, top 72% of all ranked servers.

What is the population on 2_X2 test?

Status for 2_X2 test: offline. Last seen 32 days 15 hours ago.

Server

Where does 2_X2 test sit?

No region comes from 2_X2 test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 94.183.203.31:35100.

What Rust version is 2_X2 test on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by 2_X2 test. To get in, your game needs the same protocol; Steam applies the update.

Is 2_X2 test up, and how often does it stay up?

2_X2 test reports offline. The last reading came 32 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 23 September 2026, recorded by Rust Metrics.

Rules and settings

How is 2_X2 test configured, and what rules are in force?

Gather rate check: 2x. That comes from the name 2_X2 test. The cap on groups is 100 players. The mode is survival. Note the following: the normal game: build, gather, raid. 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 2_X2 test?

Check: map. Procedural, generated by the game, on 2_X2 test.

How to join

What do you do to join 2_X2 test?

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

PLACARDS

Server tags

what each one means

Published as mp650,ptrak,$r?,v2633,gmrust,cs165217,ts100,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp650
Max players The server holds 650 slots.
ts100
Group limit You may team up with at most 100.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.