test
Offline 78.39.14.23:28015 checked 35d 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- 215/275
- 293/350
- 774/1000
- 46/100
- 866/950
- 713/800
Quick answers
from the figures on this pageWipe schedule
What wipe timing does test follow?
To tell the rhythm of test, 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 it runs now was made 35 days 3 hours ago.
Tags
How should you read the tags on test?
These are the tags test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does test appear in Rust Metrics lists and filters?
Rust Metrics lists featuring test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does test sit in the rankings?
Player hours over seven days put test at #15,436, in the top 69% of all ranked servers.
What is the population on test?
test is not responding; status offline, last seen 35 days 1 hours ago.
Operator and location
Which location does test run from?
No region tag on test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 78.39.14.23:28015.
What Rust version is test on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by test. To get in, your game needs the same protocol; Steam applies the update.
How reliable is test, and is it online now?
test reports offline. The last reading came 35 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 24 September 2026, recorded by Rust Metrics.
Map and rules
What rules does test enforce, and what are its settings?
Check: gather rate. The name test does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is test on?
Check: map. Procedural, generated by the game, on test.
Join
What do you do to join test?
To join: start Rust, press F1 and type client.connect 78.39.14.23:28015. Or press Launch Rust here and Steam opens the game and connects you.