RUST METRICSFlight deck · live data
Data live Servers11,700 Players38,590 Populated2,938 Fresh wipes 3 h91 Scan5 min
‹ All servers67.193.77.150:28015
Offline Full Queue Fresh wipe Wipe due No query

TESTING SERVER

Offline 67.193.77.150:28015 checked 5d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 0 /20

Players now

0% full 7-day avg7-day peak
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 1
Rank#14,558top 65%
Last wipe22d 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
15k10k15k20k6 Oct10 Oct14 Oct19 Oct25 Oct29 Oct

Top 65% 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
Tue 6 Oct, 02:17 UTC23d ago 0 – running 1

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 happens on TESTING SERVER when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

When does TESTING SERVER wipe?

The rhythm of TESTING SERVER's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 22 days 23 hours ago.

Tags

Which tags does TESTING SERVER carry, and what do they mean?

Tags published by TESTING SERVER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): 20 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168931 (Build): Build 168931; 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 TESTING SERVER?

Rust Metrics lists featuring TESTING SERVER: 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 TESTING SERVER hold among Rust servers?

Ranking for TESTING SERVER: #14,558 on seven-day player hours, top 65% of all ranked servers.

What is the population on TESTING SERVER?

Status for TESTING SERVER: offline. Last seen 5 days 23 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

What location is TESTING SERVER hosted in?

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

What Rust version is TESTING SERVER on?

Rust network protocol 2635 and build 168931 on Windows is the build TESTING SERVER runs. Check: protocol. To join, your game must match; Steam handles the update.

Is TESTING SERVER up, and how often does it stay up?

Check: connection. TESTING SERVER is offline at this moment. Last contact was 5 days 23 hours ago. Reading: 4% uptime over the last 7 full days. It was up 6 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does TESTING SERVER enforce, and what are its settings?

Reading the name gives no gather rate for TESTING SERVER. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TESTING SERVER?

The game generates a procedural map for TESTING SERVER.

Join

How do you connect to TESTING SERVER?

Press F1 in Rust and enter client.connect 67.193.77.150: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 mp20,ptrak,$r?,v2635,gmrust,cs168931,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp20
Max players 20 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168931
Build Build 168931.
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.