RUST METRICSFlight deck · live data
Data live Servers11,766 Players66,169 Populated3,487 Fresh wipes 3 h192 Scan5 min
‹ All servers176.103.187.206:28015
Offline Full Queue Fresh wipe Wipe due No query

Test1

Offline 176.103.187.206:28015 checked 6d ago

moddedoxide
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 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,797top 67%
Last wipe6d 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, measured since 22 Oct. 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 67% 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 6 days 20 hours ago.

Tags

How should you read the tags on Test1?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Test1. 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 Test1?

These Rust Metrics lists carry Test1: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does Test1 sit in the rankings?

Player hours over seven days put Test1 at #14,797, in the top 67% of all ranked servers.

What player count does Test1 carry?

Status for Test1: offline. Last seen 6 days 12 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

Which location does Test1 run from?

No region tag on Test1. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.103.187.206:28015.

What Rust version is Test1 on?

Reading: Test1, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Test1 reports offline. The last reading came 6 days 12 hours ago. Reading: 1% uptime over the last 6 full days. It was up 1 of 144 hours. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Test1?

No gather rate appears in the name: Test1. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test1?

Size 2,000 and seed 1337: the game generates the procedural map on Test1 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto Test1?

Press F1 in Rust and enter client.connect 176.103.187.206: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 mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.