RUST METRICSFlight deck · live data
Data live Servers11,701 Players40,419 Populated3,002 Fresh wipes 3 h95 Scan5 min
‹ All servers174.57.64.250:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Relay Test

Offline 174.57.64.250:28015 checked 38d ago

COM 1 · connect

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,073no region published
Last wipe39d 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
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
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
Sat 19 Sep, 15:16 UTC39d 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 timing

What happens on Local Relay Test when wipe day comes?

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

When does Local Relay Test wipe?

The rhythm of Local Relay 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 it runs now was made 39 days 10 hours ago.

Tags

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

Tags published by Local Relay Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Local Relay Test?

On Rust Metrics, Local Relay Test sits in these lists: 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.

Occupancy

Where does Local Relay Test sit in the rankings?

Ranking for Local Relay Test: #15,073 on seven-day player hours, top – of all ranked servers.

What player count does Local Relay Test carry?

Local Relay Test is not responding; status offline, last seen 38 days 20 hours ago.

Server details

What location is Local Relay Test hosted in?

Reading: location. Local Relay Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 174.57.64.250:28015.

What Rust version is Local Relay Test on?

Reading: Local Relay Test, Rust network protocol 2633 and build 164530, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. Local Relay Test last answered 38 days 20 hours 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 19 September 2026.

Rules and settings

How is Local Relay Test configured, and what rules are in force?

Reading the name gives no gather rate for Local Relay Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Local Relay Test on?

Procedural map on Local Relay Test, made by the game's generator.

How to join

How do you connect to Local Relay Test?

Check: join. Open Rust, press F1, then enter client.connect 174.57.64.250:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players The server holds 2 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Game build reading: 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.