RUST METRICSFlight deck · live data
Data live Servers11,652 Players47,233 Populated3,140 Fresh wipes 3 h114 Scan5 min
‹ All servers5.68.240.132:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServ

Offline 5.68.240.132:28015 checked 10d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

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,052top 59%
Last wipe24d agono schedule published
Next wipe–no rhythm it keeps
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 Sep27 Sep4 Oct11 Oct18 Oct25 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 9 OctSun 4 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 04:15 UTC20d ago 1 – running 1
Sun 4 Oct, 06:16 UTC25d ago 1 held half 4.9 days 0
Sat 3 Oct, 21:52 UTC25d ago 1 – 0.4 days 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 should you expect from wipe day on TestServ?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

When does TestServ wipe?

There is no next wipe to predict: TestServ wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 24 days 22 hours ago the current world was made.

Tag meanings

Which tags does TestServ carry, and what do they mean?

These are the tags TestServ publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 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; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TestServ?

These Rust Metrics lists carry TestServ: 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.

Population

What position does TestServ hold among Rust servers?

Player hours over seven days put TestServ at #13,052, in the top 59% of all ranked servers.

How full does TestServ get?

Reading for TestServ: offline at this moment; last seen 10 days 22 hours ago.

Operator and location

Where does TestServ sit?

No region tag on TestServ. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 5.68.240.132:28015.

What Rust version is TestServ on?

Rust network protocol 2634 and build 167781 on Windows is the build TestServ runs. Matching protocol is required to join. Let Steam update your game.

Is TestServ up, and how often does it stay up?

Reading: offline. TestServ last answered 10 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on TestServ?

No gather rate appears in the name: TestServ. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on TestServ?

Check: map. Procedural, generated by the game, on TestServ.

How to join

How do you connect to TestServ?

Check: join. Open Rust, press F1, then enter client.connect 5.68.240.132:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 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.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.