RUST METRICSFlight deck · live data
Data live Servers11,611 Players33,784 Populated2,810 Fresh wipes 3 h69 Scan5 min
‹ All servers119.252.216.50:29015
Offline Full Queue Fresh wipe Wipe due No query

ticktest

Offline 119.252.216.50:29015 checked 17d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 75 150 225 300 PAX 100 /300

Players now

33% 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#4,592top 21%
Last wipe17d 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
12k4k6k8k11 Oct12 Oct14 Oct15 Oct17 Oct18 Oct

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

wipe-day peak100players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 100, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 11:17 UTC17d ago 100 – running 30

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 should you expect from wipe day on ticktest?

The busiest point of its recent wipes drew 100 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does ticktest follow?

Its rhythm cannot be told from the wipes of ticktest 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 17 days 19 hours ago.

Lists and filters

How should you read the tags on ticktest?

Tags published by ticktest, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp300 (Max players): Slots: 300; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): Game build reading: 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does ticktest appear in Rust Metrics lists and filters?

These Rust Metrics lists carry ticktest: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Players now: At least 100.

Population

What position does ticktest hold among Rust servers?

Ranking for ticktest: #4,592 on seven-day player hours, top 21% of all ranked servers.

What is the population on ticktest?

Reading for ticktest: offline at this moment; last seen 17 days 18 hours ago.

Server details

Where does ticktest sit?

No region tag on ticktest. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 119.252.216.50:29015.

What Rust version is ticktest on?

Version check: Rust network protocol 2634 and build 167058 on Linux, run by ticktest. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on ticktest, and is it online?

Check: connection. ticktest is offline at this moment. Last contact was 17 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 11 October 2026.

Settings and map

What settings and rules apply on ticktest?

No gather rate appears in the name: ticktest. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — 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. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is off.

How to join

How can you get onto ticktest?

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

PLACARDS

Server tags

what each one means

Published as mp300,ptrak,$r?,v2634,gmrust,cs167058,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp300
Max players Slots: 300.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build Game build reading: 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.