Offline 143.110.166.24:28015 checked 8d ago
Private Token Queue 1000
Connect
srv = rust.server("143.110.166.24:28016")
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, measured since 19 Oct. 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 70% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 18:28 UTC8d ago | 0 | NaN | running | 0 |
# 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
1000 · seed 1234
- map
- Procedural Map
- size
- 1000
- seed
- 1234
Server
srv.info()- address
- 143.110.166.24:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 18:28 UTC
- hostname
- –
- first seen
- 19 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 540 on average | 621/675 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 393/425 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 312 on average | 40/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 311 on average | 50/250 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 272 on average | 157/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 99/125 |
Quick answers
From the figures on this page.
Player counts
How does Private Token Queue 1000 compare in the rankings?
Rank #15,322 on seven-day player hours for Private Token Queue 1000, within the top 70% of all ranked servers.
How full does Private Token Queue 1000 run?
Offline now for Private Token Queue 1000, with the last sample 8 days 16 hours ago.
Server data
What Rust version does Private Token Queue 1000 run?
Version Rust network protocol 2634 and build 167781 on Linux is reported by Private Token Queue 1000. Steam updates your game for you, but the protocol must match to join.
How reliable is Private Token Queue 1000, and is it online now?
The latest sample has Private Token Queue 1000 offline, with a last sighting 8 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 19 October 2026.
Which location does Private Token Queue 1000 run from?
No region is published by Private Token Queue 1000. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 143.110.166.24:28015.
Rules, settings, map
Which settings and rules does Private Token Queue 1000 run?
No gather rate appears in the name: Private Token Queue 1000. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has Private Token Queue 1000 selected?
The game generates the map on Private Token Queue 1000: procedural, size 1,000, seed 1234. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does Private Token Queue 1000 wipe?
The record for Private Token Queue 1000 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 8 days 16 hours ago.
On Private Token Queue 1000, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does Private Token Queue 1000 appear among Rust Data lists and filters?
The Rust Data lists that Private Token Queue 1000 fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Private Token Queue 1000?
These tags are published by Private Token Queue 1000 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. 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.
Join steps
What is the way into Private Token Queue 1000?
The manual route: launch Rust, F1, then client.connect 143.110.166.24:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.