RUST METRICSFlight deck · live data
Data live Servers11,622 Players33,162 Populated2,812 Fresh wipes 3 h73 Scan5 min
‹ All servers15.204.83.240:28015
Offline Full Queue Fresh wipe Wipe due No query

typical testsss

Offline 15.204.83.240:28015 checked 17d 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,702top 71%
Last wipe18d agono schedule published
Next wipe–too few wipes 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, measured since 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct12 Oct15 Oct18 Oct

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

PLAN

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

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 03:08 UTC18d 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

What happens on typical testsss when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does typical testsss wipe, and when?

Its rhythm cannot be told from the wipes of typical testsss on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 18 days 3 hours ago the current world was made.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from typical testsss. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show typical testsss?

On Rust Metrics, typical testsss sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does typical testsss hold among Rust servers?

Player hours over seven days put typical testsss at #15,702, in the top 71% of all ranked servers.

What player count does typical testsss carry?

Status for typical testsss: offline. Last seen 17 days 10 hours ago.

Server details

Where does typical testsss sit?

No region comes from typical testsss. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 15.204.83.240:28015.

What Rust version is typical testsss on?

Version check: Rust network protocol 2634 and build 167398 on Linux, run by typical testsss. Matching protocol is required to join. Let Steam update your game.

Is typical testsss up, and how often does it stay up?

Check: connection. typical testsss is offline at this moment. Last contact was 17 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 4 October 2026.

Rules and settings

What settings and rules apply on typical testsss?

Check: gather rate. The name typical testsss does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on typical testsss?

From seed 6738, the game generates the procedural map on typical testsss. Its size is 1,000. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to typical testsss?

Press F1 in Rust and enter client.connect 15.204.83.240:28015. 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 The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.