CupboardLabs Test
Offline 146.70.226.249:28015 checked 9d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 46/500
- 129/100
- 54/225
- 17/700
- 2/200
- 5/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does CupboardLabs Test follow?
To tell the rhythm of CupboardLabs Test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 13 days ago.
Tag meanings
Which tags does CupboardLabs Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from CupboardLabs Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does CupboardLabs Test appear in Rust Metrics lists and filters?
On Rust Metrics, CupboardLabs Test sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Occupancy
Where does CupboardLabs Test sit in the rankings?
Ranking for CupboardLabs Test: #15,340 on seven-day player hours, top 69% of all ranked servers.
How full does CupboardLabs Test get?
CupboardLabs Test is not responding; status offline, last seen 9 days 1 hours ago.
Server details
Which location does CupboardLabs Test run from?
No region comes from CupboardLabs Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 146.70.226.249:28015.
What Rust version is CupboardLabs Test on?
Version check: Rust network protocol 2634 and build 167781 on Windows, run by CupboardLabs Test. Check: protocol. To join, your game must match; Steam handles the update.
Is CupboardLabs Test up, and how often does it stay up?
Check: connection. CupboardLabs Test is offline at this moment. Last contact was 9 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 October 2026, recorded by Rust Metrics.
Map and rules
What rules does CupboardLabs Test enforce, and what are its settings?
Check: gather rate. The name CupboardLabs Test does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
What map is CupboardLabs Test on?
Check: map. Procedural, generated by the game, on CupboardLabs Test.
Join
How do you connect to CupboardLabs Test?
Press F1 in Rust and enter client.connect 146.70.226.249:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.