RUST METRICSFlight deck · live data
Data live Servers11,611 Players34,878 Populated2,847 Fresh wipes 3 h62 Scan5 min
‹ All servers176.43.253.48:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust 400 | Rail-Ready Standard Map

Offline 176.43.253.48:28015 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 100 200 300 400 PAX 0 /400

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,108top 70%
Last wipe68d 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 Sep27 Sep3 Oct10 Oct16 Oct23 Oct

Top 70% 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
Thu 17 Sep, 16:52 UTC40d 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

Reset cycle

What should you expect from wipe day on Rust 400 | Rail-Ready Standard Map?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

When does Rust 400 | Rail-Ready Standard Map wipe?

To tell the rhythm of Rust 400 | Rail-Ready Standard Map, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 68 days 12 hours ago the current world was made.

Tag meanings

How should you read the tags on Rust 400 | Rail-Ready Standard Map?

Tags published by Rust 400 | Rail-Ready Standard Map, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp400 (Max players): The server holds 400 slots; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Your game must run protocol 2632 to get in; cs161125 (Build): Game build reading: 161125; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Rust 400 | Rail-Ready Standard Map appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust 400 | Rail-Ready Standard Map: 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

What position does Rust 400 | Rail-Ready Standard Map hold among Rust servers?

Player hours over seven days put Rust 400 | Rail-Ready Standard Map at #15,108, in the top 70% of all ranked servers.

What is the population on Rust 400 | Rail-Ready Standard Map?

Status for Rust 400 | Rail-Ready Standard Map: offline. Last seen 11 days 17 hours ago.

Operator and location

Which location does Rust 400 | Rail-Ready Standard Map run from?

Reading: location. Rust 400 | Rail-Ready Standard Map 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 176.43.253.48:28015.

What Rust version is Rust 400 | Rail-Ready Standard Map on?

Version check: Rust network protocol 2632 and build 161125 on Windows, run by Rust 400 | Rail-Ready Standard Map. Matching protocol is required to join. Let Steam update your game.

Is Rust 400 | Rail-Ready Standard Map up, and how often does it stay up?

Rust 400 | Rail-Ready Standard Map reports offline. The last reading came 11 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Rust 400 | Rail-Ready Standard Map?

Reading the name gives no gather rate for Rust 400 | Rail-Ready Standard Map. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Rust 400 | Rail-Ready Standard Map?

Procedural map on Rust 400 | Rail-Ready Standard Map, made by the game's generator.

Connection

How can you get onto Rust 400 | Rail-Ready Standard Map?

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

PLACARDS

Server tags

what each one means

Published as mp400,ptrak,$r?,v2632,gmrust,cs161125,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp400
Max players The server holds 400 slots.
ts8
Group limit Default limit in force: 8 per team.
v2632
Protocol Your game must run protocol 2632 to get in.
cs161125
Build Game build reading: 161125.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.