TestServer
Offline 119.228.92.238:28015 checked 43d 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 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- 346/400
- 454/500
- 985/1000
- 45/100
- 983/1000
- 43/250
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TestServer follow?
The rhythm of TestServer's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 55 days 18 hours ago the current world was made.
Tags
Which tags does TestServer carry, and what do they mean?
Tags published by TestServer, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs162929 (Build): Build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TestServer?
On Rust Metrics, TestServer sits in these lists: 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 TestServer hold among Rust servers?
Ranking for TestServer: #15,488 on seven-day player hours, top – of all ranked servers.
How full does TestServer get?
Reading for TestServer: offline at this moment; last seen 43 days 1 hours ago.
Server details
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. The endpoint you need is 119.228.92.238:28015.
What Rust version is TestServer on?
Version check: Rust network protocol 2633 and build 162929 on Windows, run by TestServer. Matching protocol is required to join. Let Steam update your game.
What is the uptime on TestServer, and is it online?
TestServer reports offline. The last reading came 43 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.
Settings and map
What settings and rules apply on TestServer?
Check: gather rate. The name TestServer does not state one. 8 players per group, the default value. 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. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TestServer?
Check: map. Procedural, generated by the game, on TestServer.
Connection
How can you get onto TestServer?
To join: start Rust, press F1 and type client.connect 119.228.92.238:28015. Or press Launch Rust here and Steam opens the game and connects you.