RUST METRICSFlight deck · live data
Data live Servers11,911 Players81,677 Populated3,856 Fresh wipes 3 h102 Scan5 min
‹ All servers86.133.64.90:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 86.133.64.90:28015 checked 29d 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,860top 71%
Last wipe31d 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
15k10k15k20k27 Sep29 Sep1 Oct2 Oct4 Oct6 Oct

Top 71% 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
Sun 27 Sep, 17:18 UTC31d 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

Wipe schedule

What should you expect from wipe day on Test Server?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Test Server wipe?

Its rhythm cannot be told from the wipes of Test Server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 31 days 3 hours ago the current world was made.

Tag meanings

Which tags does Test Server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here from Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Test Server appear in Rust Metrics lists and filters?

On Rust Metrics, Test Server sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does Test Server sit in the rankings?

Player hours over seven days put Test Server at #16,860, in the top 71% of all ranked servers.

What player count does Test Server carry?

Test Server is not responding; status offline, last seen 29 days 4 hours ago.

Operator and location

Where does Test Server sit?

Reading: location. Test Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 86.133.64.90:28015.

What Rust version is Test Server on?

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

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

Test Server reports offline. The last reading came 29 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 27 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Test Server?

No gather rate appears in the name: 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. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.

Which map is live on Test Server?

The game generates a procedural map for Test Server.

How to join

How do you connect to Test Server?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock 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.