Rust Server TrendsSeismic network · station log
Recording Stations11,640 Players32,367 Active2,784 Wipes · 3 h73 48 h

Station XX-16330 · no signal

TEST_X1000

Offline 37.26.136.61:28035 checked 27d ago

1000x moddedcarbon
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,330
top 69%
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-16330 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 gap
6.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 16:29 UTC27d ago M0.0steady 0 – – running 0
Fri 18 Sep, 09:20 UTC40d ago M0.0rising 1 held half 13.3 days 0
Thu 17 Sep, 19:07 UTC41d ago M0.0steady 1 – 0.6 days 1

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
AFTER WORK | x1000 groups of 8+ · 1000x · weekly · 5 on average
2/ 50
4/ 250
2/ 50
[US] World War Rust | X1000 | Loot++ | Monthly Wipe NA · groups of 8+ · 1000x · monthly · 2 on average
0/ 100
Demonic Rust |№2|X1000|PVP|TP|DRONES|FPS+ groups of 50+ · 1000x · 2 on average
0/ 90
[DE] Battlearena x1000 #Kit #Zombies and more ... groups of 8+ · 1000x · 1 on average
0/ 16
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on TEST_X1000?

A procedural map runs on TEST_X1000, generated by the game.

Which settings and rules apply on TEST_X1000?

Its name points to a gather rate of 1000x on TEST_X1000. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on TEST_X1000 right now?

A reading taken now finds TEST_X1000 offline; the most recent activity was 27 days 12 hours ago.

How does TEST_X1000 rank against other Rust servers?

The last seven days of player hours place TEST_X1000 at #16,330, in the top 69% of all ranked servers.

Server details

How reliably does TEST_X1000 stay online?

TEST_X1000 is down at the moment; the last recorded contact was 27 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 13 September 2026 is when Rust Server Trends first recorded it.

Which region does TEST_X1000 run from?

Nothing about a region comes from TEST_X1000. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 37.26.136.61:28035 is the address it uses.

What build of Rust does TEST_X1000 use?

On Windows, TEST_X1000 runs Rust network protocol 2633 and build 165217. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on TEST_X1000?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.

How often does TEST_X1000 wipe, and on which days?

No next wipe can be predicted for TEST_X1000, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 12 hours.

Tags

What do the server tags on TEST_X1000 mean?

Tags published by TEST_X1000 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does TEST_X1000 appear?

The Rust Server Trends lists that take in TEST_X1000 are: Rust servers above 10x gather rate and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: More than 10x.

Connecting

How do you connect to TEST_X1000?

You can connect by pressing F1 in Rust and typing client.connect 37.26.136.61:28035 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build Game build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.