Offline 47.208.99.180:28015 checked 1h ago
CupboardLabs Test
Connect
srv = rust.server("47.208.99.180: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. 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, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 05:28 UTC12d ago | 1 | NaN | running | 0 |
| 1 | Thu 15 Oct, 14:28 UTC13d 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
- 47.208.99.180:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 05:28 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 · 155 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 33/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 7/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does CupboardLabs Test rank?
Over the last seven days CupboardLabs Test sits at #15,353 on player hours, in the top 69% of ranked servers.
How full does CupboardLabs Test run?
CupboardLabs Test returns no live count at this refresh, having last been seen 1 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is CupboardLabs Test on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by CupboardLabs Test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is CupboardLabs Test, and is it online now?
CupboardLabs Test is offline at this refresh; the last response came 1 hours ago. Over the last 7 full days the hours up number 32 of 168, 19%. Rust Data logged it first on 14 October 2026.
Which location does CupboardLabs Test run from?
No region is published by CupboardLabs Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 47.208.99.180:28015 is its address.
Settings and map
Which settings and rules does CupboardLabs Test run?
The name CupboardLabs Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has CupboardLabs Test loaded?
A procedural map runs on CupboardLabs Test, generated by the game.
Wipe data
On what schedule does CupboardLabs Test wipe?
Too few wipes are on record for CupboardLabs Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 12 days 20 hours ago.
On CupboardLabs Test, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 2 hours in.
Lists and tags
Which lists on Rust Data hold CupboardLabs Test, and which filters?
The Rust Data lists that CupboardLabs Test fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on CupboardLabs Test hold?
The game's server browser reads these tags from CupboardLabs Test: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 to join CupboardLabs Test?
The manual route: launch Rust, F1, then client.connect 47.208.99.180:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.