Online 47.208.99.180:28025 checked 6m ago
CupboardLabs Test (Carbon)
Connect
srv = rust.server("47.208.99.180:28027")
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 · 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 05:29 UTC12d ago | 1 | NaN | running | 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
- 47.208.99.180:28025
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 05:29 UTC
- hostname
- –
- first seen
- 14 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 | 66/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 63/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 55/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 17/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 10/1000 |
Quick answers
From the figures on this page.
Player counts
What position does CupboardLabs Test (Carbon) take in the server rankings?
Rank #15,339 on seven-day player hours for CupboardLabs Test (Carbon), within the top 69% of all ranked servers.
What population does CupboardLabs Test (Carbon) carry?
Current row: 0 players on CupboardLabs Test (Carbon), against 4 slots. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on CupboardLabs Test (Carbon)?
Rust network protocol 2635 and build 168909 on Windows is what CupboardLabs Test (Carbon) runs. Steam updates your game for you, but the protocol must match to join.
Is CupboardLabs Test (Carbon) up, and what does its uptime show?
CupboardLabs Test (Carbon) reports itself online at the current refresh. Over the last 7 full days the hours up number 9 of 168, 5%. Rust Data logged it first on 14 October 2026.
Which location does CupboardLabs Test (Carbon) run from?
For CupboardLabs Test (Carbon), no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 47.208.99.180:28025.
Map and rules
Which settings and rules does CupboardLabs Test (Carbon) run?
You will not find a gather rate in the string CupboardLabs Test (Carbon). No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on CupboardLabs Test (Carbon)?
The game generates its map: procedural, on CupboardLabs Test (Carbon).
Wipe schedule
When does CupboardLabs Test (Carbon) wipe, and on what schedule?
A rhythm cannot be read from the wipes of CupboardLabs Test (Carbon) 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. The world it runs now was generated 12 days 17 hours ago.
On CupboardLabs Test (Carbon), what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does CupboardLabs Test (Carbon) appear among Rust Data lists and filters?
On Rust Data, CupboardLabs Test (Carbon) 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; Last wipe: In the last 2 weeks.
How should you read the server tags on CupboardLabs Test (Carbon)?
These tags are published by CupboardLabs Test (Carbon) and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to CupboardLabs Test (Carbon)?
In Rust, F1 opens the console: type client.connect 47.208.99.180:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.