TEST
Offline 195.78.100.186:28015 checked 40d ago
Server instruments
no direct query in 48 hoursPlayers now
10% 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 bestWipe 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- 246/275
- 175/200
- 32/250
- 17/250
- 41/100
- 53/200
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
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 40 days 9 hours ago.
Tags
How should you read the tags on TEST?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from TEST. 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
What position does TEST hold among Rust servers?
Player hours over seven days put TEST at #13,273, in the top – of all ranked servers.
What player count does TEST carry?
TEST is not responding; status offline, last seen 40 days 6 hours ago.
Operator and location
Which location does TEST run from?
No region comes from TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 195.78.100.186:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is TEST up, and how often does it stay up?
Check: connection. TEST is offline at this moment. Last contact was 40 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 18 September 2026.
Settings and map
What settings and rules apply on TEST?
Reading the name gives no gather rate for TEST. 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. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Check: map. Procedural, generated by the game, on TEST.
Join
What do you do to join TEST?
Check: join. Open Rust, press F1, then enter client.connect 195.78.100.186:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.