Offline 91.67.161.216:28015 checked 15d ago
Carbon Test Server
Connect
srv = rust.server("91.67.161.216:28017")
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, measured since 26 Sep. 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 best
Top 71% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 13 Oct, 13:37 UTC15d ago | 1 | NaN | running | 1 |
| 1 | Sun 4 Oct, 12:49 UTC24d ago | 1 | halved by day 2 | 9 days | 1 |
| 2 | Sat 3 Oct, 09:16 UTC25d ago | 2 | NaN | 1.1 days | 0 |
| 3 | Wed 30 Sep, 23:08 UTC27d ago | 0 | NaN | 2.4 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
1000 · seed 921410901
- map
- Procedural Map
- size
- 1000
- seed
- 921410901
Server
srv.info()- address
- 91.67.161.216:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 13:37 UTC
- hostname
- –
- first seen
- 26 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 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 102/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 128/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 98/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 30/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Population
How does Carbon Test Server compare in the rankings?
Over the last seven days Carbon Test Server sits at #15,346 on player hours, in the top 71% of ranked servers.
How many players does Carbon Test Server hold at once?
Carbon Test Server returns no live count at this refresh, having last been seen 15 days 6 hours ago.
Server facts
What Rust version does Carbon Test Server run?
Rust network protocol 2634 and build 167781 on Windows is what Carbon Test Server runs. Steam updates your game for you, but the protocol must match to join.
Is Carbon Test Server up, and what does its uptime show?
The latest sample has Carbon Test Server offline, with a last sighting 15 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 26 September 2026.
Which location does Carbon Test Server run from?
No region is published by Carbon Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 91.67.161.216:28015 is its address.
Map and rules
Which settings and rules does Carbon Test Server run?
You will not find a gather rate in the string Carbon Test Server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Carbon Test Server loaded?
The game generates the map on Carbon Test Server: procedural, size 1,000, seed 921410901. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
On what schedule does Carbon Test Server wipe?
Irregular wipe times on Carbon Test Server leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 15 days 7 hours ago.
What is wipe day on Carbon Test Server like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.
Tags, lists
Which lists on Rust Data hold Carbon Test Server, and which filters?
On Rust Data, Carbon Test Server appears in these lists: 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 Carbon Test Server?
These tags are published by Carbon Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^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.
Connecting
How can I connect to Carbon Test Server?
Enter client.connect 91.67.161.216:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.