RUST METRICSFlight deck · live data
Data live Servers11,726 Players56,761 Populated3,425 Fresh wipes 3 h136 Scan5 min
‹ All servers68.209.232.151:28035
Offline Full Queue Fresh wipe Wipe due No query

test b

Offline 68.209.232.151:28035 checked 36d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,214top 58%
Last wipe36d 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
15k10k15k20k21 Sep22 Sep24 Sep25 Sep27 Sep28 Sep

Top 58% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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
Mon 21 Sep, 03:05 UTC36d ago 1 – 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

Reset cycle

What happens on test b when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

When does test b wipe?

Its rhythm cannot be told from the wipes of test b 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. The world in play was created 36 days 20 hours ago.

Tags

How should you read the tags on test b?

Tags published by test b, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does test b appear in Rust Metrics lists and filters?

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

Player count

What position does test b hold among Rust servers?

Player hours over seven days put test b at #13,214, in the top 58% of all ranked servers.

How full does test b get?

test b is not responding; status offline, last seen 36 days 8 hours ago.

Server details

Where does test b sit?

Reading: location. test b gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 68.209.232.151:28035.

What Rust version is test b on?

Rust network protocol 2633 and build 164530 on Windows is the build test b runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is test b, and is it online now?

Check: connection. test b is offline at this moment. Last contact was 36 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does test b enforce, and what are its settings?

No gather rate appears in the name: test b. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is test b on?

Check: map. Procedural, generated by the game, on test b.

Connection

How do you connect to test b?

Press F1 in Rust and enter client.connect 68.209.232.151:28035. 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 mp1,ptrak,$r?,v2633,gmvanilla,cs164530,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build The server runs game build 164530.
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.