TTC-Verify
Offline 101.143.189.73:28015 checked 23d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
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| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 17/ 100
- 296/ 400
- 189/ 225
- 134/ 100
- 389/ 1000
- 35/ 700
Quick answers
Tags and filters
Where does TTC-Verify appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TTC-Verify: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TTC-Verify?
gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): It's on build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list TTC-Verify puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What location is TTC-Verify in?
TTC-Verify does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 101.143.189.73:28015.
How reliable is TTC-Verify?
Right now TTC-Verify is offline, having last been seen 23 days 20 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 24 September 2026.
What Rust version is TTC-Verify on?
Rust network protocol 2633 and build 165217 is what TTC-Verify runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
What schedule does TTC-Verify follow for wipes?
The wipes recorded for TTC-Verify are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 37 days 23 hours is how long ago this world came into being.
Map and rules
What settings and rules have been applied to TTC-Verify?
No gather rate appears in the name of TTC-Verify. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
Which map is active on TTC-Verify?
A procedural map, generated by the game, is in play on TTC-Verify.
Player count
Is TTC-Verify busy?
The last sighting of TTC-Verify was 23 days 20 hours ago; it is offline right now.
What position does TTC-Verify hold in the server rankings?
Over the last seven days, TTC-Verify is #15,749 by player hours, among the top 71% of all ranked servers.
Join info
How do you get into TTC-Verify?
To join, open Rust, hit F1, and enter client.connect 101.143.189.73:28015. Or click Launch Rust on this page to open the game through Steam and connect.