Offline 37.26.136.61:28035 checked 27d ago
TEST_X1000
Connect
srv = rust.server("37.26.136.61:28036")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 16:29 UTC27d ago | 0 | NaN | running | 0 |
| 1 | Fri 18 Sep, 09:20 UTC40d ago | 1 | held half | 13.3 days | 0 |
| 2 | Thu 17 Sep, 19:07 UTC41d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 37.26.136.61:28035
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 16:29 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | AFTER WORK | x1000 | groups of 8+ · 1000x · weekly · 5 on average | 4/50 |
| 1 | PARADISE RUST #1 [ X1000 | BATTLEFILD | NOLIMIT | KITS | PVP ] | groups of 36+ · 1000x · 3 on average | 2/250 |
| 2 | The Darkest Valley | 1000X | BI-WEEKLY| NO VIP | RAIDABLE BASES | groups of 8+ · 1000x · 2 on average | 3/50 |
| 3 | [US] World War Rust | X1000 | Loot++ | Monthly Wipe | NA · groups of 8+ · 1000x · monthly · 2 on average | 0/100 |
| 4 | Demonic Rust |№2|X1000|PVP|TP|DRONES|FPS+ | groups of 50+ · 1000x · 2 on average | 0/90 |
| 5 | [DE] Battlearena x1000 #Kit #Zombies and more ... | groups of 8+ · 1000x · 1 on average | 0/16 |
Quick answers
From the figures on this page.
Population data
What position does TEST_X1000 take in the server rankings?
Over the last seven days TEST_X1000 sits at #16,330 on player hours, in the top 69% of ranked servers.
How full does TEST_X1000 run?
Offline now for TEST_X1000, with the last sample 27 days 7 hours ago.
Server facts
What is the Rust version on TEST_X1000?
Rust network protocol 2633 and build 165217 on Windows is what TEST_X1000 runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TEST_X1000, and is it up?
TEST_X1000 is offline at this refresh; the last response came 27 days 7 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does TEST_X1000 sit?
For TEST_X1000, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 37.26.136.61:28035.
Rules, settings, map
What rules and settings are recorded for TEST_X1000?
1000x gather is what the name states, and the name is TEST_X1000. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has TEST_X1000 selected?
A procedural map runs on TEST_X1000, generated by the game.
Wipe schedule
On what schedule does TEST_X1000 wipe?
TEST_X1000 wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 27 days 7 hours ago, and that is the one in play.
On TEST_X1000, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.
Lists and tags
Which lists on Rust Data hold TEST_X1000, and which filters?
On Rust Data, TEST_X1000 appears in these lists: Modded Rust servers and Rust servers with more than 10x. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: More than 10x.
Which meanings do the tags on TEST_X1000 hold?
The game's server browser reads these tags from TEST_X1000: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join TEST_X1000?
The manual route: launch Rust, F1, then client.connect 37.26.136.61:28035. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.