Holds a respectable place: #4,592 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 98 places this week.
A steady term.
Strongest in standing (B); momentum is the one to work on (D).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 11:17 UTC18d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
ticktest leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 119.252.216.50:29015 is the address to use.
Is ticktest up, and how steady is its uptime?
At this moment, ticktest is offline; the last time it was seen was 18 days 2 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 11 October 2026.
What Rust version is ticktest on?
Rust network protocol 2634 and build 167058 on Linux is what ticktest runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does ticktest wipe, and how often?
The record holds too few of ticktest's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 18 days 2 hours.
What happens on ticktest when wipe day arrives?
The average peak on its recent wipes was 100 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does ticktest place in the wider field of Rust servers?
In the top 21% of all ranked servers, ticktest sits at #4,592 for player hours over the last seven days.
How many players does ticktest usually have?
ticktest is offline at the moment; the last time it was seen was 18 days 2 hours ago.
Tags
What is meant by the tags on ticktest?
The game's browser takes its cue from the tags ticktest has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp300 (Max players): 300 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167058 (Build): This runs on build 167058; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show ticktest?
Rust Server Score lists that include ticktest: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Players now: At least 100.
Map and rules
Which rules does ticktest enforce, and what are its settings?
The name of ticktest gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are not covered by VAC, Valve's anti-cheat.
Getting in
What is the way to join ticktest?
To connect, start Rust, press F1, and type client.connect 119.252.216.50:29015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2634,gmrust,cs167058,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp300
Max players300 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167058
BuildThis runs on build 167058.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin 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.
A steady term. Strongest in standing (B); momentum is the one to work on (D).