Testserver
Offline 120.29.24.30:28015 checked 30d ago
Server instruments
no direct query in 48 hoursPlayers now
20% 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 61% 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- 270/325
- 331/425
- 0/8
- 850/1000
- 52/100
- 914/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Testserver follow?
Its rhythm cannot be told from the wipes of Testserver on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 30 days 12 hours ago.
Tag meanings
How should you read the tags on Testserver?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Testserver. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Testserver?
These Rust Metrics lists carry Testserver: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does Testserver sit in the rankings?
Player hours over seven days put Testserver at #14,559, in the top 61% of all ranked servers.
How full does Testserver get?
Testserver is not responding; status offline, last seen 30 days 12 hours ago.
Operator and location
Where does Testserver sit?
No region comes from Testserver. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 120.29.24.30:28015.
What Rust version is Testserver on?
Reading: Testserver, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Testserver, and is it online?
Reading: offline. Testserver last answered 30 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 29 September 2026, recorded by Rust Metrics.
Settings and map
What rules does Testserver enforce, and what are its settings?
No gather rate appears in the name: Testserver. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
How to join
How do you connect to Testserver?
Press F1 in Rust and enter client.connect 120.29.24.30:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.