RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h83 Scan5 min
‹ All servers74.12.199.102:28015
Offline Full Queue Fresh wipe Wipe due No query

TESTING123

Offline 74.12.199.102:28015 checked 21d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#13,751top 62%
Last wipe21d 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
RankRank in region
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 62% 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

Wipe schedule

When does TESTING123 wipe?

The rhythm of TESTING123's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 21 days 11 hours ago.

Lists and filters

How should you read the tags on TESTING123?

These are the tags TESTING123 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; 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): Check: category. Modded, because plugins or settings alter the game. 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 TESTING123?

These Rust Metrics lists carry TESTING123: 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

Where does TESTING123 sit in the rankings?

Player hours over seven days put TESTING123 at #13,751, in the top 62% of all ranked servers.

What player count does TESTING123 carry?

Status for TESTING123: offline. Last seen 21 days 9 hours ago.

Server details

What location is TESTING123 hosted in?

No region comes from TESTING123. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 74.12.199.102:28015.

What Rust version is TESTING123 on?

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

How reliable is TESTING123, and is it online now?

Reading: offline. TESTING123 last answered 21 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 7 October 2026, recorded by Rust Metrics.

Rules and settings

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

Check: gather rate. The name TESTING123 does not state one. 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. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TESTING123?

The game generates a procedural map for TESTING123.

Join

How can you get onto TESTING123?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
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 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.