RUST METRICSFlight deck · live data
Data live Servers11,694 Players52,148 Populated3,104 Fresh wipes 3 h109 Scan5 min
‹ All servers96.42.119.158:28115
Offline Full Queue Fresh wipe Wipe due No query

rstest-local

Offline 96.42.119.158:28115 checked 17d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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#15,427top 71%
Last wipe17d 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 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 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
Mon 12 Oct, 23:23 UTC17d ago 0 – 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 happens on rstest-local 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 rstest-local wipe?

The rhythm of rstest-local's wipes cannot be told yet: too few are on record. 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 17 days ago.

Tags

How should you read the tags on rstest-local?

Tags published by rstest-local, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does rstest-local appear in Rust Metrics lists and filters?

On Rust Metrics, rstest-local sits in these lists: 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.

Player count

What position does rstest-local hold among Rust servers?

Ranking for rstest-local: #15,427 on seven-day player hours, top 71% of all ranked servers.

What player count does rstest-local carry?

Status for rstest-local: offline. Last seen 17 days ago.

Server

Where does rstest-local sit?

No region comes from rstest-local. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 96.42.119.158:28115.

What Rust version is rstest-local on?

Rust network protocol 2634 and build 167398 on Windows is the build rstest-local runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is rstest-local, and is it online now?

rstest-local reports offline. The last reading came 17 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 12 October 2026.

Map and rules

How is rstest-local configured, and what rules are in force?

Reading the name gives no gather rate for rstest-local. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Connection

How do you connect to rstest-local?

To join: start Rust, press F1 and type client.connect 96.42.119.158:28115. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players 2 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.