RUST METRICSFlight deck · live data
Data live Servers11,650 Players32,278 Populated2,796 Fresh wipes 3 h79 Scan5 min
‹ All servers212.133.232.105:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER | 3X | [TR]

Offline 212.133.232.105:28015 checked 45d ago

3x moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 38 75 112 150 PAX 1 /150

Players now

1% 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–score 0
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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
No rank history yet.
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

What wipe timing does TEST SERVER | 3X | [TR] follow?

Its rhythm cannot be told from the wipes of TEST SERVER | 3X | [TR] 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. The world it runs now was made 48 days 14 hours ago.

Tags

Which tags does TEST SERVER | 3X | [TR] carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163493 (Build): The server runs game build 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from TEST SERVER | 3X | [TR]. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show TEST SERVER | 3X | [TR]?

These Rust Metrics lists carry TEST SERVER | 3X | [TR]: 3x Rust servers, checked live and Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

Population

What player count does TEST SERVER | 3X | [TR] carry?

TEST SERVER | 3X | [TR] is not responding; status offline, last seen 45 days 20 hours ago.

Server details

Where does TEST SERVER | 3X | [TR] sit?

No region tag on TEST SERVER | 3X | [TR]. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 212.133.232.105:28015.

What Rust version is TEST SERVER | 3X | [TR] on?

Reading: TEST SERVER | 3X | [TR], Rust network protocol 2633 and build 163493, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is TEST SERVER | 3X | [TR] up, and how often does it stay up?

Check: connection. TEST SERVER | 3X | [TR] is offline at this moment. Last contact was 45 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is TEST SERVER | 3X | [TR] configured, and what rules are in force?

Gather rate check: 3x. That comes from the name TEST SERVER | 3X | [TR]. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is TEST SERVER | 3X | [TR] on?

The game generates a procedural map for TEST SERVER | 3X | [TR].

How to join

How do you connect to TEST SERVER | 3X | [TR]?

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

PLACARDS

Server tags

what each one means

Published as mp150,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp150
Max players The server holds 150 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163493
Build The server runs game build 163493.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.