RUST METRICSFlight deck · live data
Data live Servers11,867 Players96,005 Populated3,901 Fresh wipes 3 h390 Scan5 min
‹ All servers186.189.244.234:28015
Offline Full Queue Fresh wipe Wipe due No query

Tata

Offline 186.189.244.234:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg7-day peak
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 1
Rank#14,330top 64%
Last wipe21d 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
15k10k15k20k28 Sep4 Oct10 Oct16 Oct23 Oct29 Oct

Top 64% 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 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
Wed 7 Oct, 16:38 UTC21d ago 1 – running 1

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

What should you expect from wipe day on Tata?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Tata follow?

Its rhythm cannot be told from the wipes of Tata 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 21 days 23 hours ago.

Tags

How should you read the tags on Tata?

Tags published by Tata, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Tata appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Tata: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Tata hold among Rust servers?

Player hours over seven days put Tata at #14,330, in the top 64% of all ranked servers.

What is the population on Tata?

Status for Tata: offline. Last seen 6 days 8 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server details

Where does Tata sit?

Reading: location. Tata gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 186.189.244.234:28015.

What Rust version is Tata on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by Tata. Matching protocol is required to join. Let Steam update your game.

How reliable is Tata, and is it online now?

Check: connection. Tata is offline at this moment. Last contact was 6 days 8 hours ago. Reading: 1% uptime over the last 7 full days. It was up 2 of 168 hours. Check: first contact. Rust Metrics logged it on 28 September 2026.

Rules and settings

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

Reading the name gives no gather rate for Tata. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. 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 Tata?

The game generates a procedural map for Tata.

Join

What do you do to join Tata?

Press F1 in Rust and enter client.connect 186.189.244.234:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.