RUST METRICSFlight deck · live data
Data live Servers11,622 Players31,880 Populated2,774 Fresh wipes 3 h73 Scan5 min
‹ All servers212.102.62.171:28015
Offline Full Queue Fresh wipe Wipe due No query

test1

Offline 212.102.62.171:28015 checked 5d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% 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 average1peak 1
Rank#14,050top 63%
Last wipe24d 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
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

Top 63% 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

Wipe timing

What wipe timing does test1 follow?

To tell the rhythm of test1, too few of its wipes are on record. 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 it runs now was made 24 days 20 hours ago.

Tags

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

Tags published by test1, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): 15 slots in total; ts8 (Group limit): Default limit in force: 8 per team; 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): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does test1 appear in Rust Metrics lists and filters?

On Rust Metrics, test1 sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does test1 sit in the rankings?

Ranking for test1: #14,050 on seven-day player hours, top 63% of all ranked servers.

How full does test1 get?

test1 is not responding; status offline, last seen 5 days 17 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

Where does test1 sit?

No region comes from test1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 212.102.62.171:28015.

What Rust version is test1 on?

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

Is test1 up, and how often does it stay up?

test1 reports offline. The last reading came 5 days 17 hours ago. Uptime for the last 5 full days: 0 of 120 hours, or 0%. The first sighting on Rust Metrics was 23 October 2026.

Settings and map

What rules does test1 enforce, and what are its settings?

No gather rate appears in the name: test1. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on test1?

The game generates a procedural map for test1.

How to join

How can you get onto test1?

Press F1 in Rust and enter client.connect 212.102.62.171: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 mp15,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players 15 slots in total.
ts8
Group limit Default limit in force: 8 per team.
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 Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.