cbtest
Offline 140.232.64.4:28015 checked 17d ago
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 70% 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
- 834/ 100
- 111/ 400
- 101/ 245
- 130/ 100
- 255/ 1000
- 18/ 700
Quick answers
Tags and search
Where does cbtest appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry cbtest are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on cbtest?
gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): It's on build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list cbtest puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What location is cbtest in?
No region comes from cbtest. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 140.232.64.4:28015.
What's the uptime like for cbtest?
The server cbtest is not reachable at the moment; the last sighting was 17 days 21 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 30 September 2026.
What Rust version is cbtest on?
Rust network protocol 2633 and build 165217 is what cbtest runs, on Linux. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does cbtest follow for wipes?
cbtest's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 17 days 21 hours is how long ago this world came into being.
Rules and settings
What settings are in place on cbtest?
No gather rate appears in the name of cbtest. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
What's the map on cbtest?
The map on cbtest is procedural, made by the game.
Player count
Is cbtest busy?
Right now cbtest is offline, with its last appearance 17 days 21 hours ago.
Where does cbtest sit in the rankings?
For player hours in the last seven days, cbtest ranks #16,838, within the top 70% of ranked servers.
Join info
How do you get into cbtest?
To join, open Rust, hit F1, and enter client.connect 140.232.64.4:28015. Or click Launch Rust on this page to open the game through Steam and connect.