Offline 119.252.216.50:29015 checked 17d ago
ticktest
Connect
srv = rust.server("119.252.216.50:29017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 100, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 11:17 UTC17d ago | 100 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- CraggyIsland
- size
- –
- seed
- –
Server
srv.info()- address
- 119.252.216.50:29015
- region
- –
- max players
- 300
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 11:17 UTC
- hostname
- –
- first seen
- 11 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 78/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 124/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 40/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 15/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does ticktest rank?
Player hours over seven days put ticktest at #4,592, in the top 21% of the ranked set.
What population does ticktest carry?
The current row shows ticktest offline; the last response was 17 days 19 hours ago.
About the server
Which Rust version is ticktest on?
Rust network protocol 2634 and build 167058 on Linux is what ticktest runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is ticktest, and is it up?
The latest sample has ticktest offline, with a last sighting 17 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 11 October 2026.
In which location is ticktest hosted?
There is no region published for ticktest. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 119.252.216.50:29015.
Rules, settings, map
Which settings and rules does ticktest run?
You will not find a gather rate in the string ticktest. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC is not running; Valve's anti-cheat is off.
Wipes and dates
On what schedule does ticktest wipe?
The record for ticktest holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 17 days 20 hours ago.
On ticktest, what happens on wipe day?
The average peak over recent wipes is 100 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold ticktest, and which filters?
These Rust Data lists include ticktest: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Players now: At least 100.
Which meanings do the tags on ticktest hold?
These tags are published by ticktest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp300 (Max players): The server lists 300 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into ticktest?
Enter client.connect 119.252.216.50:29015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.