Test
Offline 178.234.107.177:28015 checked 27d 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 60% 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- 383/425
- 463/500
- 983/1000
- 57/100
- 987/1000
- 26/250
Quick answers
from the figures on this pageWipe timing
How often does Test wipe, and when?
Its rhythm cannot be told from the wipes of Test on record: there are too few. 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 27 days 23 hours ago.
Lists and filters
How should you read the tags on Test?
These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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?
On Rust Metrics, Test sits in these lists: 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
What position does Test hold among Rust servers?
Ranking for Test: #13,897 on seven-day player hours, top 60% of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 27 days 22 hours ago.
Server
Which location does Test run from?
No region comes from Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 178.234.107.177:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 164530 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?
Check: connection. Test is offline at this moment. Last contact was 27 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.
Settings and map
How is Test configured, and what rules are in force?
No gather rate appears in the name: Test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. 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?
Check: map. Procedural, generated by the game, on Test.
How to join
What do you do to join Test?
Check: join. Open Rust, press F1, then enter client.connect 178.234.107.177:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.