Working its way up from the back of the class: #15,322 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
48/ 100
D
Slipped a little: down 662 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% 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 peak0players, 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 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 18:28 UTC9d ago
0
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Private Token Queue 1000 based in?
Private Token Queue 1000 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 143.110.166.24:28015.
How dependable is Private Token Queue 1000, and is it online at the moment?
At this moment, Private Token Queue 1000 is offline; the last time it was seen was 9 days 2 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 19 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Private Token Queue 1000 sit?
Rust network protocol 2634 and build 167781 on Linux is what Private Token Queue 1000 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Private Token Queue 1000 wipe, and how often?
There are too few wipes on record for Private Token Queue 1000 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 9 days 2 hours.
What happens on Private Token Queue 1000 when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Private Token Queue 1000 place in the wider field of Rust servers?
Over the last seven days, Private Token Queue 1000 has #15,322 for player hours, in the top 70% of all ranked servers.
How many players does Private Token Queue 1000 usually have?
Private Token Queue 1000 is offline at the moment; the last time it was seen was 9 days 2 hours ago.
Lists and filters
What is meant by the tags on Private Token Queue 1000?
The game's browser takes its cue from the tags Private Token Queue 1000 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Private Token Queue 1000?
Rust Server Score lists that include Private Token Queue 1000: Best community servers, graded. It shows under the following 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.
Server rules
How is Private Token Queue 1000 set up, and what rules does it keep?
Nothing in the name of Private Token Queue 1000 states a 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. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Private Token Queue 1000?
The game generates the procedural map on Private Token Queue 1000 at size 1,000 with seed 1234. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Private Token Queue 1000?
To connect, start Rust, press F1, and type client.connect 143.110.166.24:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 term to build on. Strongest in momentum (D); standing is the one to work on (F).