RUST METRICSFlight deck · live data
Data live Servers11,840 Players80,134 Populated3,897 Fresh wipes 3 h160 Scan5 min
‹ All servers136.49.50.202:28515
Offline Full Queue Fresh wipe Wipe due No query

o13 test

Offline 136.49.50.202:28515 checked 7d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,326top 69%
Last wipe7d 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
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 69% 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 timing

How often does o13 test wipe, and when?

Its rhythm cannot be told from the wipes of o13 test 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 7 days 23 hours ago.

Tag meanings

How should you read the tags on o13 test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here from o13 test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show o13 test?

Rust Metrics lists featuring o13 test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does o13 test hold among Rust servers?

Player hours over seven days put o13 test at #15,326, in the top 69% of all ranked servers.

How full does o13 test get?

Status for o13 test: offline. Last seen 7 days 23 hours ago.

Server

Which location does o13 test run from?

No region comes from o13 test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 136.49.50.202:28515.

What Rust version is o13 test on?

Version check: Rust network protocol 2634 and build 167781 on Linux, run by o13 test. Matching protocol is required to join. Let Steam update your game.

What is the uptime on o13 test, and is it online?

Reading: offline. o13 test last answered 7 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 October 2026.

Rules and settings

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

No gather rate appears in the name: o13 test. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

Which map is live on o13 test?

The game generates a procedural map for o13 test.

Join

What do you do to join o13 test?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players The server holds 2 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.