Station XX-13072 · no signal
My Carbon Test Server
Offline 8.9.83.129:25566 checked 13d ago
- Players now
- 1/ 50
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,072
- top 61%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- 1d 20h
- Thu 29 Oct, 16:05 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
a steady gapNext wipe Thursday 29 October, 16:05 UTC, in 1d 20h. Every 7 days 21 hours · medium confidence
- usual gap
- 7.9 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 67%else halves by day 1
Coming wipes
- 1d 20hThu 29 Oct, 16:05 UTC
- 8d 23hThu 5 Nov, 19:00 UTCFW
- 9d 16hFri 6 Nov, 12:57 UTC
- 17d 13hSat 14 Nov, 09:49 UTC
- 25d 10hSun 22 Nov, 06:40 UTC
- 33d 7hMon 30 Nov, 03:32 UTC
- 36d 23hThu 3 Dec, 19:00 UTCFW
- 41d 4hTue 8 Dec, 00:23 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 13 Oct, 22:22 UTC13d ago | M0.0▲rising | 1 | – | running | 0 | |
| Tue 6 Oct, 01:31 UTC21d ago | M0.0■steady | 1 | halved by day 1 | 7.9 days | 1 | |
| Mon 28 Sep, 19:38 UTC29d ago | M0.0■steady | 1 | held half | 7.2 days | 1 | |
| Sun 20 Sep, 20:42 UTC36d ago | M0.0■steady | 1 | held half | 8 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on My Carbon Test Server?
A procedural map runs on My Carbon Test Server, generated by the game.
Which settings and rules apply on My Carbon Test Server?
You will find no gather rate in the name of My Carbon Test Server. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on My Carbon Test Server?
My Carbon Test Server is not responding at this moment and is offline, last seen 13 days 20 hours ago.
How does My Carbon Test Server rank against other Rust servers?
The last seven days of player hours place My Carbon Test Server at #13,072, in the top 61% of all ranked servers.
Operator and location
How reliably does My Carbon Test Server stay online?
As recorded now, My Carbon Test Server is not reachable, the last contact having been 13 days 20 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 16 September 2026 is when Rust Server Trends first recorded it.
Which region does My Carbon Test Server run from?
A region is not published by My Carbon Test Server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 8.9.83.129:25566 is the address it uses.
What build of Rust does My Carbon Test Server use?
Rust network protocol 2634 and build 167781 on Windows is what My Carbon Test Server runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on My Carbon Test Server?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 67% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
On what timetable does My Carbon Test Server run its wipes?
About every 7.9 days is how often My Carbon Test Server has wiped lately. The date of its next wipe is Thursday 29 October at 16:05 UTC. 13 days 21 hours is how long the current world has been running.
Server tags
What do the server tags on My Carbon Test Server mean?
Tags published by My Carbon Test Server and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $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): A plugin framework, Carbon, runs 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 My Carbon Test Server appear?
The Rust Server Trends lists that take in My Carbon Test Server are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How to join
What steps get you onto My Carbon Test Server?
To join, enter client.connect 8.9.83.129:25566 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
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.