RUST METRICSFlight deck · live data
Data live Servers11,674 Players57,845 Populated3,415 Fresh wipes 3 h99 Scan5 min
‹ All servers85.193.35.88:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 85.193.35.88:28015 checked 37d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#13,917no region published
Last wipe43d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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 peak2players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 14 Sep, 14:44 UTC43d ago 2 – 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 timing

What should you expect from wipe day on Test?

At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 1 hours in.

When does Test wipe?

Its rhythm cannot be told from the wipes of Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 43 days 19 hours ago.

Tags

How should you read the tags on Test?

Tags published by Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Test sit in the rankings?

Ranking for Test: #13,917 on seven-day player hours, top – of all ranked servers.

What player count does Test carry?

Status for Test: offline. Last seen 37 days 12 hours ago.

Server details

Where does Test sit?

Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 85.193.35.88:28015.

What Rust version is Test on?

Reading: Test, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Test, and is it online?

Reading: offline. Test last answered 37 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is Test configured, and what rules are in force?

No gather rate appears in the name: Test. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Test on?

Procedural map on Test, made by the game's generator.

How to join

How do you connect to Test?

To join: start Rust, press F1 and type client.connect 85.193.35.88:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
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.