test server
Offline 223.104.48.149:28015 checked 31d 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 72% 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- 164/250
- 96/200
- 15/250
- 17/250
- 12/100
- 17/200
Quick answers
from the figures on this pageWipe timing
When does test server wipe?
To tell the rhythm of test server, too few of its wipes are on record. 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 31 days 22 hours ago.
Tags
How should you read the tags on test server?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from test server. 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 test server?
These Rust Metrics lists carry test server: 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 test server sit in the rankings?
Ranking for test server: #16,921 on seven-day player hours, top 72% of all ranked servers.
What player count does test server carry?
Status for test server: offline. Last seen 31 days 22 hours ago.
Server
Which location does test server run from?
No region tag on test server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 223.104.48.149:28015.
What Rust version is test server on?
Reading: test server, Rust network protocol 2633 and build 165217, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is test server up, and how often does it stay up?
Reading: offline. test server last answered 31 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 27 September 2026.
Rules and settings
What settings and rules apply on test server?
Check: gather rate. The name test server does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is test server on?
Procedural map on test server, made by the game's generator.
Connection
What do you do to join test server?
Press F1 in Rust and enter client.connect 223.104.48.149:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.