RUST METRICSFlight deck · live data
Data live Servers11,612 Players36,584 Populated2,915 Fresh wipes 3 h70 Scan5 min
‹ All servers194.50.170.87:28015
Offline Full Queue Fresh wipe Wipe due No query

My test SERVER

Offline 194.50.170.87: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 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,339top 69%
Last wipe15d 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
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

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

How often does My test SERVER wipe, and when?

Its rhythm cannot be told from the wipes of My test SERVER on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 15 days 22 hours ago.

Tag meanings

Which tags does My test SERVER carry, and what do they mean?

Tags published by My test SERVER, 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): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. 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 My test SERVER?

These Rust Metrics lists carry My test SERVER: 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

Where does My test SERVER sit in the rankings?

Ranking for My test SERVER: #15,339 on seven-day player hours, top 69% of all ranked servers.

How full does My test SERVER get?

My test SERVER is not responding; status offline, last seen 6 days 11 hours ago. Check: player average. 0 over the last seven days.

Server details

What location is My test SERVER hosted in?

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

What Rust version is My test SERVER on?

Reading: My test SERVER, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is My test SERVER up, and how often does it stay up?

Reading: offline. My test SERVER last answered 6 days 11 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. Check: first contact. Rust Metrics logged it on 22 October 2026.

Map and rules

What settings and rules apply on My test SERVER?

Reading the name gives no gather rate for My test SERVER. The group cap is 8 players, which is the default in the game. 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. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on My test SERVER?

Check: map. Procedural, generated by the game, on My test SERVER.

Join

How can you get onto My test SERVER?

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

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 The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.