RUST METRICSFlight deck · live data
Data live Servers11,595 Players34,229 Populated2,837 Fresh wipes 3 h65 Scan5 min
‹ All servers45.45.237.10:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing 0123456

Offline 45.45.237.10:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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#16,013top 69%
Last wipe39d 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 19 Sep. 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 Sep24 Sep27 Sep1 Oct4 Oct8 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

Wipe timing

When does Testing 0123456 wipe?

The rhythm of Testing 0123456's wipes cannot be told yet: too few 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 in play was created 39 days ago.

Lists and filters

Which tags does Testing 0123456 carry, and what do they mean?

These are the tags Testing 0123456 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Testing 0123456 appear in Rust Metrics lists and filters?

On Rust Metrics, Testing 0123456 sits in these lists: 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.

Population

What position does Testing 0123456 hold among Rust servers?

Player hours over seven days put Testing 0123456 at #16,013, in the top 69% of all ranked servers.

What is the population on Testing 0123456?

Testing 0123456 is not responding; status offline, last seen 26 days 6 hours ago.

Server

Where does Testing 0123456 sit?

No region tag on Testing 0123456. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 45.45.237.10:28015.

What Rust version is Testing 0123456 on?

Reading: Testing 0123456, Rust network protocol 2633 and build 164530, Linux. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Testing 0123456, and is it online?

Check: connection. Testing 0123456 is offline at this moment. Last contact was 26 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.

Rules and settings

What rules does Testing 0123456 enforce, and what are its settings?

Reading the name gives no gather rate for Testing 0123456. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Testing 0123456 on?

Size 1,000 and seed 1: the game generates the procedural map on Testing 0123456 from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join Testing 0123456?

Press F1 in Rust and enter client.connect 45.45.237.10: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 mp40,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players 40 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.