RUST METRICSFlight deck · live data
Data live Servers11,842 Players74,292 Populated3,699 Fresh wipes 3 h224 Scan5 min
‹ All servers190.111.127.52:28015
Offline Full Queue Fresh wipe Wipe due No query

TagMapServer

Offline 190.111.127.52:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,326top 69%
Last wipe6d 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
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 69% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 19:48 UTC6d 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

Reset cycle

What happens on TagMapServer when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does TagMapServer follow?

To tell the rhythm of TagMapServer, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 6 days 18 hours ago.

Lists and filters

Which tags does TagMapServer carry, and what do they mean?

These are the tags TagMapServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.

Which lists and filters on Rust Metrics show TagMapServer?

These Rust Metrics lists carry TagMapServer: 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; Last wipe: In the last week.

Player count

Where does TagMapServer sit in the rankings?

Ranking for TagMapServer: #15,326 on seven-day player hours, top 69% of all ranked servers.

What player count does TagMapServer carry?

Reading for TagMapServer: offline at this moment; last seen 6 days 18 hours ago. Check: player average. 0 over the last seven days.

Server

Which location does TagMapServer run from?

No region comes from TagMapServer. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 190.111.127.52:28015.

What Rust version is TagMapServer on?

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

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

Check: connection. TagMapServer is offline at this moment. Last contact was 6 days 18 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. The first sighting on Rust Metrics was 22 October 2026.

Map and rules

What settings and rules apply on TagMapServer?

No gather rate appears in the name: TagMapServer. 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. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is TagMapServer on?

Procedural map on TagMapServer, made by the game's generator.

Connection

What do you do to join TagMapServer?

Check: join. Open Rust, press F1, then enter client.connect 190.111.127.52:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.