RUST METRICSFlight deck · live data
Data live Servers11,635 Players46,883 Populated3,179 Fresh wipes 3 h98 Scan5 min
‹ All servers96.55.44.196:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Test

Offline 96.55.44.196:28015 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 0 /8

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,956top 71%
Last wipe21d 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
15k10k15k20k23 Sep26 Sep29 Sep8 Oct11 Oct14 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.

usual gap14 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctWed 23 Sep
00.250.50.751+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
Wed 7 Oct, 03:11 UTC21d ago 0 – running 1
Wed 23 Sep, 03:48 UTC35d ago 1 – 14 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 happens on Local Rust Test when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Local Rust Test follow?

The rhythm of Local Rust Test'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 21 days 5 hours ago.

Tag meanings

How should you read the tags on Local Rust Test?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp8 (Max players): Slots: 8; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166655 (Build): The server runs game build 166655; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Local Rust Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

On Rust Metrics, Local Rust Test sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does Local Rust Test sit in the rankings?

Ranking for Local Rust Test: #15,956 on seven-day player hours, top 71% of all ranked servers.

What player count does Local Rust Test carry?

Status for Local Rust Test: offline. Last seen 21 days 2 hours ago.

Server details

Which location does Local Rust Test run from?

No region comes from Local Rust Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 96.55.44.196:28015.

What Rust version is Local Rust Test on?

Rust network protocol 2634 and build 166655 on Windows is the build Local Rust Test runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Local Rust Test, and is it online now?

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

Settings and map

What settings and rules apply on Local Rust Test?

No gather rate appears in the name: Local Rust Test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Local Rust Test?

The game generates a procedural map for Local Rust Test.

Join

How do you connect to Local Rust Test?

Press F1 in Rust and enter client.connect 96.55.44.196: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 mp8,ptrak,$r?,v2634,gmrust,cs166655,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp8
Max players Slots: 8.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166655
Build The server runs game build 166655.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.