RUST METRICSFlight deck · live data
Data live Servers11,767 Players74,585 Populated3,497 Fresh wipes 3 h237 Scan5 min
‹ All servers15.204.83.240:28017
Offline Full Queue Fresh wipe Wipe due No query

typical TESTq

Offline 15.204.83.240:28017 checked 19d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,858top 72%
Last wipe22d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k7 Oct9 Oct11 Oct13 Oct15 Oct17 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does typical TESTq wipe, and when?

To tell the rhythm of typical TESTq, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 22 days 17 hours ago the current world was made.

Tags

Which tags does typical TESTq carry, and what do they mean?

Tags published by typical TESTq, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show typical TESTq?

Rust Metrics lists featuring typical TESTq: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does typical TESTq hold among Rust servers?

Ranking for typical TESTq: #15,858 on seven-day player hours, top 72% of all ranked servers.

What player count does typical TESTq carry?

typical TESTq is not responding; status offline, last seen 19 days ago.

Server

Which location does typical TESTq run from?

No region tag on typical TESTq. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 15.204.83.240:28017.

What Rust version is typical TESTq on?

Reading: typical TESTq, Rust network protocol 2634 and build 167398, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is typical TESTq, and is it online now?

typical TESTq reports offline. The last reading came 19 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 7 October 2026.

Map and rules

What settings and rules apply on typical TESTq?

No gather rate appears in the name: typical TESTq. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is typical TESTq on?

Check: map. Procedural, generated by the game, on typical TESTq.

Connection

How do you connect to typical TESTq?

Press F1 in Rust and enter client.connect 15.204.83.240:28017. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.