TEST
Offline 46.55.81.200: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- 673/700
- 432/475
- 36/250
- 61/250
- 215/200
- 127/150
Quick answers
from the figures on this pageWipe timing
What wipe timing does TEST follow?
The rhythm of TEST'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. The world it runs now was made 42 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; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $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. 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.
Population
Where does TEST sit in the rankings?
Ranking for TEST: #15,498 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 1 hours ago.
Server details
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. The endpoint you need is 46.55.81.200:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 42 days 1 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 16 September 2026.
Map and rules
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
Join
How do you connect to TEST?
Press F1 in Rust and enter client.connect 46.55.81.200:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.