Offline 101.143.189.73:28015 checked 35d ago
TTC-Verify
Connect
srv = rust.server("101.143.189.73:28017")
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 101.143.189.73:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Sep 2026, 11:27 UTC
- hostname
- –
- first seen
- 24 Sep 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 | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 92/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 244/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 344/350 |
Quick answers
From the figures on this page.
Player counts
How does TTC-Verify compare in the rankings?
Rank #15,749 on seven-day player hours for TTC-Verify, within the top 71% of all ranked servers.
How full does TTC-Verify run?
TTC-Verify returns no live count at this refresh, having last been seen 35 days 1 hours ago.
About the server
What Rust version does TTC-Verify run?
Version Rust network protocol 2633 and build 165217 on Linux is reported by TTC-Verify. The protocol has to match before you can join, and Steam does the updating.
Is TTC-Verify up, and what does its uptime show?
TTC-Verify is offline at this refresh; the last response came 35 days 1 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 24 September 2026.
In which location is TTC-Verify hosted?
There is no region published for TTC-Verify. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 101.143.189.73:28015 is its address.
Settings and map
Which rules apply on TTC-Verify, and what settings?
You will not find a gather rate in the string TTC-Verify. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has TTC-Verify loaded?
A procedural map runs on TTC-Verify, generated by the game.
Wipe data
When does TTC-Verify wipe, and how often?
A rhythm cannot be read from the wipes of TTC-Verify on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 49 days 5 hours ago.
Tags and filters
Which lists on Rust Data hold TTC-Verify, and which filters?
The Rust Data lists that TTC-Verify fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on TTC-Verify hold?
The game's server browser reads these tags from TTC-Verify: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join TTC-Verify?
The manual route: launch Rust, F1, then client.connect 101.143.189.73:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.