test
Offline 83.23.140.41:28015 checked 29d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 61% 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- 317/350
- 20/250
- 38/250
- 141/200
- 53/200
- 47/100
Quick answers
from the figures on this pageReset cycle
How often does test wipe, and when?
To tell the rhythm of test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 30 days 12 hours ago.
Tags
Which tags does test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 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; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does test appear in Rust Metrics lists and filters?
These Rust Metrics lists carry test: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does test sit in the rankings?
Ranking for test: #14,543 on seven-day player hours, top 61% of all ranked servers.
What player count does test carry?
Status for test: offline. Last seen 29 days 12 hours ago.
Server
Which location does test run from?
No region tag on test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 83.23.140.41:28015.
What Rust version is test on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by test. Matching protocol is required to join. Let Steam update your game.
Is test up, and how often does it stay up?
Check: connection. test is offline at this moment. Last contact was 29 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 28 September 2026.
Map and rules
What rules does test enforce, and what are its settings?
Reading the name gives no gather rate for test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
Which map is live on test?
Procedural map on test, made by the game's generator.
Connection
How do you connect to test?
Press F1 in Rust and enter client.connect 83.23.140.41:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.