Test Server
Offline 78.190.138.130:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
100% 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- 453/475
- 364/375
- 43/250
- 31/250
- 52/100
- 151/200
Quick answers
from the figures on this pageWipe schedule
When does Test Server wipe?
Its rhythm cannot be told from the wipes of Test Server on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 41 days 20 hours ago the current world was made.
Lists and filters
How should you read the tags on Test Server?
Tags published by Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $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 Server appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Test Server: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does Test Server hold among Rust servers?
Ranking for Test Server: #14,325 on seven-day player hours, top – of all ranked servers.
What is the population on Test Server?
Test Server is not responding; status offline, last seen 41 days 19 hours ago.
Operator and location
Where does Test Server sit?
No region tag on Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 78.190.138.130:28015.
What Rust version is Test Server on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by Test Server. 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 41 days 19 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 17 September 2026.
Rules and settings
How is Test Server configured, and what rules are in force?
Check: gather rate. The name Test Server does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. 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.
What map is Test Server on?
Check: map. Procedural, generated by the game, on Test Server.
Connection
What do you do to join Test Server?
Check: join. Open Rust, press F1, then enter client.connect 78.190.138.130:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.