Offline 195.133.63.209:28015 checked 14d ago
Sector 17 - Carbon Test
Connect
srv = rust.server("195.133.63.209:28016")
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 | Wed 14 Oct, 08:30 UTC14d ago | 0 | NaN | running | 1 |
| 1 | Tue 13 Oct, 20:46 UTC14d ago | 1 | NaN | 0.5 days | 0 |
# 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
- 195.133.63.209:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 08:30 UTC
- hostname
- –
- first seen
- 12 Oct 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 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Sector 17 - Carbon Test take in the server rankings?
Rank #15,208 on seven-day player hours for Sector 17 - Carbon Test, within the top 70% of all ranked servers.
How full does Sector 17 - Carbon Test run?
Offline now for Sector 17 - Carbon Test, with the last sample 14 days 11 hours ago.
Server data
Which Rust version is Sector 17 - Carbon Test on?
The build is Rust network protocol 2634 and build 167584 on Windows, run by Sector 17 - Carbon Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Sector 17 - Carbon Test, and is it online now?
The latest sample has Sector 17 - Carbon Test offline, with a last sighting 14 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 12 October 2026.
Where does Sector 17 - Carbon Test sit?
No region is published by Sector 17 - Carbon Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 195.133.63.209:28015 is its address.
Map and rules
Which settings and rules does Sector 17 - Carbon Test run?
No gather rate appears in the name: Sector 17 - Carbon Test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has Sector 17 - Carbon Test loaded?
Sector 17 - Carbon Test runs a procedural map, which the game generates.
Wipe schedule
When does Sector 17 - Carbon Test wipe, and how often?
A rhythm cannot be read from the wipes of Sector 17 - Carbon Test on record, which are too few. 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 14 days 11 hours ago, and that is the one in play.
On Sector 17 - Carbon Test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain Sector 17 - Carbon Test?
These Rust Data lists include Sector 17 - Carbon Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Sector 17 - Carbon Test?
The game's server browser reads these tags from Sector 17 - Carbon Test: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into Sector 17 - Carbon Test?
Enter client.connect 195.133.63.209:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.