TM_Server_RU
Online 31.130.13.0:28015 checked 9m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 17/ 100
- 260/ 400
- 178/ 225
- 132/ 100
- 392/ 1000
- 31/ 700
Quick answers
Tags and filters
Where does TM_Server_RU appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TM_Server_RU: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on TM_Server_RU?
TM_Server_RU's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): There are 100 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): Plugins are handled by Carbon. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
Where can you find TM_Server_RU?
TM_Server_RU does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 31.130.13.0:28015.
What's the uptime like for TM_Server_RU?
TM_Server_RU is up and reachable at the moment. Rust Going Deep has had it on record since 18 October 2026.
What Rust version is TM_Server_RU on?
The version on TM_Server_RU is Rust network protocol 2634 and build 167781, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does TM_Server_RU follow for wipes?
The wipes recorded for TM_Server_RU are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 15 days 21 hours ago.
Map and rules
What settings and rules have been applied to TM_Server_RU?
No gather rate appears in the name of TM_Server_RU. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser puts it under Modded, as plugins or settings alter the game. You will find Carbon plugins installed. VAC is on: Valve's anti-cheat is active.
What's the map on TM_Server_RU?
The map on TM_Server_RU is procedural, made by the game.
Population
What's the population like on TM_Server_RU?
Right now 0 players are on TM_Server_RU, which has 100 slots. The seven-day average is 0 players, with a peak of 1. The busiest point in the last 48 hours was 12:00 UTC, averaging 1 players.
Where does TM_Server_RU sit in the rankings?
For player hours in the last seven days, TM_Server_RU ranks #12,972, within the top 59% of ranked servers.
Join info
How do you get into TM_Server_RU?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 31.130.13.0:28015.