Rust Data LabData lab · live
Live readings Servers11,669 Players53,688 Populated3,358 Fresh wipes · 3h87 Sampled every 5 min

Element card · group Community · atomic number 15,322, its rank

Private Token Queue 1000

Offline 143.110.166.24:28015 checked 8d ago

Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak –
Rank · atomic number#15,322top 70%
Last wipe8d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k19 Oct20 Oct22 Oct23 Oct25 Oct26 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 18:28 UTC8d 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

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 500
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 540 on average 500/ 250
  2. 2 Ru Rustoria.co - … 313
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average 313/ 325
  3. 3 Ru Rustoria.co - … 35
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 314 on average 35/ 250
  4. 4 Ru Rusty Moose |E… 35
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 313 on average 35/ 250
  5. 5 Ru Rustoria.co - … 157
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 273 on average 157/ 200
  6. 6 Ru Rustafied.com … 75
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average 75/ 100

Quick answers

from the figures on this page

Settings and map

What map is in play on Private Token Queue 1000?

Private Token Queue 1000 runs a procedural map of size 1,000 with seed 1234; the game generates it. You can view it on RustMaps from this page, since matching size and seed produce the same map.

What rules has Private Token Queue 1000 set, and what settings are in force?

Nothing in the name of Private Token Queue 1000 gives a gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. You will find it under Community in the server browser. The VAC anti-cheat from Valve is enabled.

Server facts

Which location is Private Token Queue 1000 based in?

No region is published by Private Token Queue 1000. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 143.110.166.24:28015.

What Rust version does Private Token Queue 1000 currently run?

On Linux, Private Token Queue 1000 is running Rust network protocol 2634 and build 167781. Joining requires the same protocol on your game; Steam takes care of updating it.

How dependable is Private Token Queue 1000 for staying online?

Private Token Queue 1000 is not online at the moment; the last sighting was 8 days 15 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. The first sighting by Rust Data Lab was on 19 October 2026.

Wipes and resets

What is the wiping pattern on Private Token Queue 1000?

The record holds too few of Private Token Queue 1000's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. 8 days 15 hours ago the current world was made.

How does Private Token Queue 1000 look on the day of a wipe?

At their busiest, recent wipes averaged 0 players. Peak numbers on the latest wipe came 0 hours in.

Tags, lists

What should you understand from the tags Private Token Queue 1000 carries?

The game's server browser reads the tags Private Token Queue 1000 publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): It has 10 slots; ts8 (Group limit): 8 per team, the default the game ships with; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): A region code has not been set here. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does Private Token Queue 1000 come up?

These themed Rust Data Lab lists carry Private Token Queue 1000: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player counts

Against other Rust servers, where does Private Token Queue 1000 place?

The seven-day player-hours table has Private Token Queue 1000 at #15,322, in the top 70% of ranked servers.

What does the current player count on Private Token Queue 1000 tell you?

Private Token Queue 1000 is offline at the moment; the last sighting was 8 days 15 hours ago.

Getting on

What steps get you onto Private Token Queue 1000?

In Rust, press F1 and enter client.connect 143.110.166.24:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players It has 10 slots.
ts8
Group limit 8 per team, the default the game ships with.
v2634
Protocol To join, your game must match protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code A region code has not been set here.

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.