test
Offline 140.122.178.123:28015 checked 42d 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- 366/425
- 459/500
- 981/1000
- 59/100
- 989/1000
- 27/250
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. 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 43 days 1 hours ago.
Tags
How should you read the tags on test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $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?
On Rust Metrics, test sits in these lists: 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.
Player count
What position does test hold among Rust servers?
Ranking for test: #15,481 on seven-day player hours, top – of all ranked servers.
How full does test get?
test is not responding; status offline, last seen 42 days 4 hours ago.
Operator and location
What location is test hosted in?
Reading: location. test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 140.122.178.123:28015.
What Rust version is test on?
Rust network protocol 2633 and build 163794 on Windows is the build test runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on test, and is it online?
Reading: offline. test last answered 42 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Rules and settings
How is test configured, and what rules are in force?
Check: gather rate. The name test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
What map is test on?
The game generates a procedural map for test.
Connection
How do you connect to test?
Press F1 in Rust and enter client.connect 140.122.178.123:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.