RUST METRICSFlight deck · live data
Data live Servers11,767 Players74,585 Populated3,497 Fresh wipes 3 h237 Scan5 min
‹ All servers101.143.189.73:28015
Offline Full Queue Fresh wipe Wipe due No query

TTC-Verify

Offline 101.143.189.73:28015 checked 35d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

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

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,749top 71%
Last wipe49d 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
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 Oct

Top 71% 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 TTC-Verify wipe?

To tell the rhythm of TTC-Verify, too few of its wipes are on record. 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 49 days 11 hours ago.

Lists and filters

How should you read the tags on TTC-Verify?

Check: tags. The game's server browser reads 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; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from TTC-Verify. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TTC-Verify appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TTC-Verify: 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.

Player count

What position does TTC-Verify hold among Rust servers?

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

What is the population on TTC-Verify?

TTC-Verify is not responding; status offline, last seen 35 days 7 hours ago.

Server details

Which location does TTC-Verify run from?

No region tag on TTC-Verify. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 101.143.189.73:28015.

What Rust version is TTC-Verify on?

Reading: TTC-Verify, Rust network protocol 2633 and build 165217, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on TTC-Verify, and is it online?

Check: connection. TTC-Verify is offline at this moment. Last contact was 35 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on TTC-Verify?

No gather rate appears in the name: TTC-Verify. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is TTC-Verify on?

The game generates a procedural map for TTC-Verify.

Connection

What do you do to join TTC-Verify?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,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.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.