test
Offline 188.146.134.14:28015 checked 31d 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- 434/500
- 457/475
- 981/1000
- 64/100
- 989/1000
- 23/250
Quick answers
from the figures on this pageReset cycle
What wipe timing does test follow?
The rhythm of test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 32 days 3 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): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show test?
Rust Metrics lists featuring test: 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.
Occupancy
What position does test hold among Rust servers?
Player hours over seven days put test at #14,533, in the top 61% of all ranked servers.
What is the population on test?
test is not responding; status offline, last seen 31 days 17 hours ago.
Server details
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 188.146.134.14:28015.
What Rust version is test on?
Rust network protocol 2633 and build 165217 on Windows is the build test runs. Check: protocol. To join, your game must match; Steam handles the update.
Is test up, and how often does it stay up?
Check: connection. test is offline at this moment. Last contact was 31 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 27 September 2026, recorded by Rust Metrics.
Map and rules
How is test configured, and what rules are in force?
No gather rate appears in the name: test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on test?
The game generates a procedural map for test.
Connection
What do you do to join test?
To join: start Rust, press F1 and type client.connect 188.146.134.14:28015. Or press Launch Rust here and Steam opens the game and connects you.