RUST METRICSFlight deck · live data
Data live Servers11,741 Players62,626 Populated3,351 Fresh wipes 3 h195 Scan5 min
‹ All servers186.123.147.251:28015
Offline Full Queue Fresh wipe Wipe due No query

Mi Servidor RusTesting

Offline 186.123.147.251:28015 checked 43d 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 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,462no region published
Last wipe43d 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
15k10k15k20k20 Sep21 Sep22 Sep
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

Reset cycle

When does Mi Servidor RusTesting wipe?

Its rhythm cannot be told from the wipes of Mi Servidor RusTesting on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 43 days 12 hours ago.

Lists and filters

How should you read the tags on Mi Servidor RusTesting?

Tags published by Mi Servidor RusTesting, 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; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Mi Servidor RusTesting?

Rust Metrics lists featuring Mi Servidor RusTesting: 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.

Occupancy

What position does Mi Servidor RusTesting hold among Rust servers?

Ranking for Mi Servidor RusTesting: #15,462 on seven-day player hours, top – of all ranked servers.

How full does Mi Servidor RusTesting get?

Mi Servidor RusTesting is not responding; status offline, last seen 43 days 11 hours ago.

Server

Where does Mi Servidor RusTesting sit?

No region tag on Mi Servidor RusTesting. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 186.123.147.251:28015.

What Rust version is Mi Servidor RusTesting on?

Version check: Rust network protocol 2633 and build 163794 on Linux, run by Mi Servidor RusTesting. Matching protocol is required to join. Let Steam update your game.

Is Mi Servidor RusTesting up, and how often does it stay up?

Check: connection. Mi Servidor RusTesting is offline at this moment. Last contact was 43 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 15 September 2026.

Map and rules

What settings and rules apply on Mi Servidor RusTesting?

Reading the name gives no gather rate for Mi Servidor RusTesting. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on Mi Servidor RusTesting?

Check: map. Procedural, generated by the game, on Mi Servidor RusTesting.

How to join

How can you get onto Mi Servidor RusTesting?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs163794,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.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Build 163794.
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.