RUST METRICSFlight deck · live data
Data live Servers11,753 Players67,907 Populated3,403 Fresh wipes 3 h209 Scan5 min
‹ All servers51.210.34.129:28035
Offline Full Queue Fresh wipe Wipe due No query

Rust Beyond | Test Server

Offline 51.210.34.129:28035 checked 28d ago

moddedcarbon
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#16,032top 69%
Last wipe30d 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 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

Top 69% 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 gap6.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 29 SepSun 27 SepWed 16 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 21:44 UTC30d ago 1 – running 0
Sun 27 Sep, 16:33 UTC32d ago 1 halved by day 1 2.2 days 0
Wed 16 Sep, 16:47 UTC43d ago 0 – 11 days 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 Rust Beyond | Test Server?

An average of 1 players came at the busiest on its recent wipes. 1 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 1 it fell below half when it didn't.

What wipe timing does Rust Beyond | Test Server follow?

No next wipe can be predicted for Rust Beyond | Test Server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 30 days 1 hours ago the current world was made.

Tag meanings

How should you read the tags on Rust Beyond | Test Server?

These are the tags Rust Beyond | Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. 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 Rust Beyond | Test Server?

Rust Metrics lists featuring Rust Beyond | Test Server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does Rust Beyond | Test Server sit in the rankings?

Player hours over seven days put Rust Beyond | Test Server at #16,032, in the top 69% of all ranked servers.

What player count does Rust Beyond | Test Server carry?

Reading for Rust Beyond | Test Server: offline at this moment; last seen 28 days 3 hours ago.

Server details

Where does Rust Beyond | Test Server sit?

No region comes from Rust Beyond | Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 51.210.34.129:28035.

What Rust version is Rust Beyond | Test Server on?

Rust network protocol 2633 and build 165217 on Linux is the build Rust Beyond | Test Server runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Rust Beyond | Test Server, and is it online?

Check: connection. Rust Beyond | Test Server is offline at this moment. Last contact was 28 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Settings and map

How is Rust Beyond | Test Server configured, and what rules are in force?

Reading the name gives no gather rate for Rust Beyond | Test Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

What map is Rust Beyond | Test Server on?

Check: map. Procedural, generated by the game, on Rust Beyond | Test Server.

How to join

What do you do to join Rust Beyond | Test Server?

Press F1 in Rust and enter client.connect 51.210.34.129: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.