Skip to the page
Network live 11,803 servers online 69,659 players aboard 128 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

TEST_X1000

Offline 37.26.136.61:28035 checked 26d ago

1000x moddedcarbon
Tracking number · connect
Wipe progress · wiped 26d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 50 players now 0% full
07-day averagepeak –
#16,330ranktop 69%
26d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

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.

6.9 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
100%crowd heldof 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.

Wipes

every wipe as a delivery, newest first
  1. Thu 1 Oct, 16:29 UTC 17:29 UK · 26d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Fri 18 Sep, 09:20 UTC 10:20 UK · 39d ago
    Wipe delivered
    Peak
    1
    Crowd
    held half
    Lasted
    13.3 days
    Players before
    0
  3. Thu 17 Sep, 19:07 UTC 20:07 UK · 40d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    0.6 days
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. AFTER WORK | x1000groups of 8+ · 1000x · weekly · 5 on average 4 / 50
  2. PARADISE RUST #1 [ X1000 | BATTLEFILD | NOLIMIT | KITS | PVP ]groups of 36+ · 1000x · 4 on average 3 / 250
  3. The Darkest Valley | 1000X | BI-WEEKLY| NO VIP | RAIDABLE BASESgroups of 8+ · 1000x · 2 on average 2 / 50
  4. [US] World War Rust | X1000 | Loot++ | Monthly WipeNA · groups of 8+ · 1000x · monthly · 2 on average 2 / 100
  5. Demonic Rust |№2|X1000|PVP|TP|DRONES|FPS+groups of 50+ · 1000x · 2 on average 0 / 90
  6. [DE] Battlearena x1000 #Kit #Zombies and more ...groups of 8+ · 1000x · 1 on average 0 / 16
Help desk

Quick answers

From the figures on this page.

Population

How does TEST_X1000 compare with other Rust servers in the rankings?

Over the past seven days, TEST_X1000 has climbed to #16,330 for player hours, putting it in the top 69% of all ranked servers.

How many players are on TEST_X1000 right now?

The last sighting of TEST_X1000 was 26 days 5 hours ago; it is offline right now.

Server rules

On what map does TEST_X1000 take place?

A procedural map, generated by the game, is what TEST_X1000 runs.

Which settings and rules apply on TEST_X1000?

Gather rate on TEST_X1000 is 1000x, as its name says. Up to 8 players can join a group, the default for the game. It runs survival, the usual game: build, gather, raid. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.

About the server

What is the location of TEST_X1000?

You will find no region published by TEST_X1000. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 37.26.136.61:28035.

How reliable is TEST_X1000, and is it currently online?

Offline for now: TEST_X1000 was last seen 26 days 5 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. It was first seen by Rust Wipe Tracker on 13 September 2026.

On what Rust version does TEST_X1000 operate?

Rust network protocol 2633 and build 165217 on Windows is what TEST_X1000 runs. The same protocol is required to join, and Steam takes care of updating it.

Map resets

How does TEST_X1000 handle its wipe days?

At their busiest, its recent wipes drew an average of 1 players. On the latest wipe, 0 hours passed before the crowd peaked. Half the peak or more was held until the next wipe in 100% of recent wipes.

When does TEST_X1000 wipe? What schedule does it follow?

No next wipe can be predicted for TEST_X1000, which wipes at irregular times. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. The world it is running was made 26 days 5 hours.

Tags and listings

On Rust Wipe Tracker, which lists and filters is TEST_X1000 part of?

The Rust Wipe Tracker lists that include TEST_X1000 are: Rust servers above 10x gather and Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: More than 10x.

What is the meaning of the server tags on TEST_X1000?

gmrust (Game mode): Standard Rust survival is the game mode here; mp50 (Max players): Slot count: 50; ts8 (Group limit): 8 per team, which is the default; v2633 (Protocol): To join, your game must match protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; ^y (Carbon): Carbon, a plugin framework, is installed here are the tags TEST_X1000 publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Getting started

What is the process to join TEST_X1000?

Enter client.connect 37.26.136.61:28035 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game mode here.
mp50
Max players Slot count: 50.
ts8
Group limit 8 per team, which is the default.
v2633
Protocol To join, your game must match protocol 2633.
cs165217
Build The game build is 165217.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code A region code isn't set.

Mods and access

^z
Modded The game is changed by plugins or settings, hence the Modded listing.
^y
Carbon Carbon, a plugin framework, is installed 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.