RUST METRICSFlight deck · live data
Data live Servers11,599 Players34,406 Populated2,900 Fresh wipes 3 h67 Scan5 min
‹ All servers92.4.133.57:28015
Offline Full Queue Fresh wipe Wipe due No query

localbench

Offline 92.4.133.57:28015 checked 5d ago

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#15,419top 69%
Last wipe5d 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
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 69% 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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 22:03 UTC5d 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 timing

What should you expect from wipe day on localbench?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does localbench wipe, and when?

The rhythm of localbench's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 5 days 7 hours ago.

Tags

How should you read the tags on localbench?

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): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from localbench. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does localbench appear in Rust Metrics lists and filters?

Rust Metrics lists featuring localbench: 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; Last wipe: In the last week.

Player count

What position does localbench hold among Rust servers?

Ranking for localbench: #15,419 on seven-day player hours, top 69% of all ranked servers.

What player count does localbench carry?

Status for localbench: offline. Last seen 5 days 7 hours ago. Check: player average. 0 over the last seven days.

Operator and location

Which location does localbench run from?

Reading: location. localbench gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 92.4.133.57:28015.

What Rust version is localbench on?

Reading: localbench, Rust network protocol 2634 and build 167781, Linux. To get in, your game needs the same protocol; Steam applies the update.

How reliable is localbench, and is it online now?

localbench reports offline. The last reading came 5 days 7 hours ago. Uptime for the last 5 full days: 0 of 120 hours, or 0%. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Rules and settings

How is localbench configured, and what rules are in force?

No gather rate appears in the name: localbench. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is localbench on?

The game generates a procedural map for localbench.

Join

How do you connect to localbench?

Press F1 in Rust and enter client.connect 92.4.133.57: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?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
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.