RUST METRICSFlight deck · live data
Data live Servers11,612 Players35,778 Populated2,872 Fresh wipes 3 h59 Scan5 min
‹ All servers31.130.13.0:28015
Offline Full Queue Fresh wipe Wipe due No query

TM_Server_RU

Offline 31.130.13.0:28015 checked 9d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 1 /100

Players now

1% 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#13,003top 59%
Last wipe25d agono schedule published
Next wipe–no wipe 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
15k10k15k20k18 Oct19 Oct21 Oct22 Oct24 Oct25 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 schedule

When does TM_Server_RU wipe?

Its rhythm cannot be told from the wipes of TM_Server_RU on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 25 days 10 hours ago.

Lists and filters

How should you read the tags on TM_Server_RU?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon from TM_Server_RU. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TM_Server_RU appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TM_Server_RU: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

What position does TM_Server_RU hold among Rust servers?

Ranking for TM_Server_RU: #13,003 on seven-day player hours, top 59% of all ranked servers.

How full does TM_Server_RU get?

Status for TM_Server_RU: offline. Last seen 9 days 8 hours ago.

Operator and location

Where does TM_Server_RU sit?

Reading: location. TM_Server_RU gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 31.130.13.0:28015.

What Rust version is TM_Server_RU on?

Rust network protocol 2634 and build 167781 on Windows is the build TM_Server_RU runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on TM_Server_RU, and is it online?

Check: connection. TM_Server_RU is offline at this moment. Last contact was 9 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 October 2026.

Rules and settings

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

No gather rate appears in the name: TM_Server_RU. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TM_Server_RU?

The game generates a procedural map for TM_Server_RU.

Join

How can you get onto TM_Server_RU?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.