RUST METRICSFlight deck · live data
Data live Servers11,610 Players40,842 Populated2,876 Fresh wipes 3 h140 Scan5 min
‹ All servers76.133.251.206:31015
Offline Full Queue Fresh wipe Wipe due No query

tmp653

Offline 76.133.251.206:31015 checked 39d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,502no 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 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
Sun 20 Sep, 15:56 UTC39d 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 tmp653?

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

When does tmp653 wipe?

The rhythm of tmp653's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 39 days 14 hours ago the current world was made.

Lists and filters

How should you read the tags on tmp653?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Match the game version: protocol 2632 is required; cs161125 (Build): Game build reading: 161125; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from tmp653. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does tmp653 appear in Rust Metrics lists and filters?

On Rust Metrics, tmp653 sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does tmp653 sit in the rankings?

Ranking for tmp653: #15,502 on seven-day player hours, top – of all ranked servers.

What is the population on tmp653?

Reading for tmp653: offline at this moment; last seen 39 days 14 hours ago.

Server details

What location is tmp653 hosted in?

No region comes from tmp653. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 76.133.251.206:31015.

What Rust version is tmp653 on?

Reading: tmp653, Rust network protocol 2632 and build 161125, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is tmp653, and is it online now?

Reading: offline. tmp653 last answered 39 days 14 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 20 September 2026.

Settings and map

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

Check: gather rate. The name tmp653 does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is tmp653 on?

Check: map. Procedural, generated by the game, on tmp653.

How to join

What do you do to join tmp653?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2632
Protocol Match the game version: protocol 2632 is required.
cs161125
Build Game build reading: 161125.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.