test1
Offline 185.156.53.135:26165 checked 41d 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, measured since 17 Sep. 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- 166/500
- 123/100
- 181/225
- 71/700
- 13/200
- 21/1000
Quick answers
from the figures on this pageReset cycle
How often does test1 wipe, and when?
To tell the rhythm of test1, 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. 51 days 19 hours ago the current world was made.
Tags
How should you read the tags on test1?
These are the tags test1 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): The server runs game build 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show test1?
On Rust Metrics, test1 sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does test1 hold among Rust servers?
Player hours over seven days put test1 at #15,413, in the top – of all ranked servers.
What is the population on test1?
test1 is not responding; status offline, last seen 41 days 5 hours ago.
Operator and location
Where does test1 sit?
No region comes from test1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 185.156.53.135:26165.
What Rust version is test1 on?
Rust network protocol 2633 and build 163207 on Linux is the build test1 runs. Matching protocol is required to join. Let Steam update your game.
How reliable is test1, and is it online now?
test1 reports offline. The last reading came 41 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on test1?
No gather rate appears in the name: test1. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
Which map is live on test1?
Size 3,000 and seed 159753: the game generates the procedural map on test1 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How can you get onto test1?
Press F1 in Rust and enter client.connect 185.156.53.135:26165. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.