TestServer
Offline 79.117.21.248:28015 checked 2d 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- 531/575
- 430/475
- 274/250
- 58/100
- 359/250
- 393/350
Quick answers
from the figures on this pageReset cycle
What wipe timing does TestServer follow?
To tell the rhythm of TestServer, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 2 days 6 hours ago.
Lists and filters
How should you read the tags on TestServer?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; v2275 (Protocol): Protocol 2275: join only on the same game version; ptrak (Networking): RakNet carries the traffic, as standard for Rust; h232a393a (Custom tag): This tag is non-standard, added by the owner or a plugin; stok (Custom tag): This tag is non-standard, added by the owner or a plugin from TestServer. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does TestServer appear in Rust Metrics lists and filters?
Rust Metrics lists featuring 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; Last wipe: In the last 3 days.
Population
Where does TestServer sit in the rankings?
Player hours over seven days put TestServer at #15,335, in the top 69% of all ranked servers.
What player count does TestServer carry?
TestServer is not responding; status offline, last seen 2 days 5 hours ago. Check: player average. 0 over the last seven days.
Operator and location
What location is TestServer hosted in?
No region comes from TestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 79.117.21.248:28015.
What Rust version is TestServer on?
Rust network protocol 2275 on Windows is the build TestServer runs. Check: protocol. To join, your game must match; Steam handles the update.
Is TestServer up, and how often does it stay up?
Reading: offline. TestServer last answered 2 days 5 hours ago. Uptime for the last 1 full day: 0 of 24 hours, or 0%. Reading: first seen 27 October 2026, recorded by Rust Metrics.
Rules and settings
How is TestServer configured, and what rules are in force?
Check: gather rate. The name TestServer does not state one. No group limit is published. Mode check gives survival; gather, build and raid, as the game normally runs. 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 79.117.21.248:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.