hyper-testbed
Key statistics
the figures behind the quote- Players now
- 0/ 50 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 4 peak 60
- Rank
- #5,220 top 23%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 3d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 44 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 Oct 2026 no hostname published
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 23% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 60 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 60, 17 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 11 Oct, 07:18 UTC3d ago | 60 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 52/300 | ▲+38+277.4% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 67/225 | ▲+26+64.4% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+2+1.9% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 88 on average | 11/1000 | ▼−5−30.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 5/1000 | ▪+0−4.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 25/700 | ▲+2+9.1% |
Quick answers
from the figures on this pageMap and Rules
What settings and rules are in place on hyper-testbed?
No gather rate is given in the name of hyper-testbed. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Carbon. VAC is active.
Which map is played on hyper-testbed?
A procedural map runs on hyper-testbed, created by the game.
Population
Where does hyper-testbed sit in the rankings?
For the last seven days, hyper-testbed holds rank #5,220 on player hours, in the top 23% of all ranked servers.
What is the population on hyper-testbed?
Right now, hyper-testbed is offline; the last sighting was 2 days 21 hours ago. The seven-day average is 4 players, with a peak of 60.
Wipe Schedule
How does hyper-testbed handle wipe day?
An average of 60 players marked the busiest point of its recent wipes. On the latest wipe, 17 hours after the wipe, the crowd peaked.
On what cycle does hyper-testbed wipe?
The record holds too few of hyper-testbed's wipes to establish its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 3 days 14 hours.
Server Overview
What is the server location for hyper-testbed?
There is no region published for hyper-testbed. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 144.6.242.42:28015 is its address.
hyper-testbed runs which version of Rust?
Rust network protocol 2634 and build 167398 on Windows is what hyper-testbed runs. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of hyper-testbed?
No response from hyper-testbed. It was last seen 2 days 21 hours ago. 12% is its uptime for the last 3 full days, 9 of 72 hours. 10 October 2026 is when Rust Analytics first saw it.
Tags & Filters
What is the meaning of the tags on hyper-testbed?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp50 (Max players): It holds 50 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167398 (Build): It runs build 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; ^y (Carbon): The plugin framework here is Carbon, which hyper-testbed publishes. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does hyper-testbed show up in Rust Analytics lists and filters?
The following Rust Analytics lists feature hyper-testbed: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Joining the Server
What steps do I take to join hyper-testbed?
Type client.connect 144.6.242.42:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y
Game
gmrust
mp50
ts8
v2634
cs167398
ptrak
$r?
Mods and access
^z
^y
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.