RUST METRICSFlight deck · live data
Data live Servers11,814 Players74,934 Populated3,774 Fresh wipes 3 h144 Scan5 min
‹ All servers37.26.136.61:28035
Offline Full Queue Fresh wipe Wipe due No query

TEST_X1000

Offline 37.26.136.61:28035 checked 26d ago

1000x moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,330top 69%
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k20 Sep23 Sep26 Sep2 Oct5 Oct8 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap6.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 1 OctFri 18 SepThu 17 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 16:29 UTC26d ago 0 – running 0
Fri 18 Sep, 09:20 UTC39d ago 1 held half 13.3 days 0
Thu 17 Sep, 19:07 UTC40d ago 1 – 0.6 days 1

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 schedule

What should you expect from wipe day on TEST_X1000?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does TEST_X1000 wipe, and when?

There is no next wipe to predict: TEST_X1000 wipes at irregular times. 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 26 days 5 hours ago.

Tags

How should you read the tags on TEST_X1000?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon from TEST_X1000. 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 TEST_X1000?

Rust Metrics lists featuring TEST_X1000: Gather rate above 10x: server list and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: More than 10x.

Occupancy

What position does TEST_X1000 hold among Rust servers?

Ranking for TEST_X1000: #16,330 on seven-day player hours, top 69% of all ranked servers.

What is the population on TEST_X1000?

Reading for TEST_X1000: offline at this moment; last seen 26 days 5 hours ago.

Operator and location

Where does TEST_X1000 sit?

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

What Rust version is TEST_X1000 on?

Rust network protocol 2633 and build 165217 on Windows is the build TEST_X1000 runs. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. TEST_X1000 last answered 26 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on TEST_X1000?

The name carries the rate: 1000x gather on TEST_X1000. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

What map is TEST_X1000 on?

Check: map. Procedural, generated by the game, on TEST_X1000.

Connection

How do you connect to TEST_X1000?

Press F1 in Rust and enter client.connect 37.26.136.61:28035. 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 mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.