Station XX-15323 · no signal
TEST COPY (update check)
Offline 171.254.141.176:28025 checked 4d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,323
- top 69%
- Last wipe
- 9d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
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 69% 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on TEST COPY (update check)?
The map on TEST COPY (update check) is procedural, produced by the game.
Which settings and rules apply on TEST COPY (update check)?
The name of TEST COPY (update check) gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on TEST COPY (update check)?
TEST COPY (update check) is not responding at this moment and is offline, last seen 4 days 23 hours ago. The population averaged 0 players over the past week.
How does TEST COPY (update check) rank against other Rust servers?
On player hours for the past week, TEST COPY (update check) sits at #15,323, which puts it inside the top 69% of every ranked server.
Server details
How reliably does TEST COPY (update check) stay online?
TEST COPY (update check) is down at the moment; the last recorded contact was 4 days 23 hours ago. It was up 0% of the time across the last 4 full days: 0 of 96 hours. Its earliest appearance in the records of Rust Server Trends dates to 24 October 2026.
Where in the world is TEST COPY (update check) hosted?
A region is not published by TEST COPY (update check). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 171.254.141.176:28025.
What build of Rust does TEST COPY (update check) use?
On Windows, TEST COPY (update check) runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
How often does TEST COPY (update check) wipe, and on which days?
On record so far are too few of TEST COPY (update check)'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 9 days 19 hours.
Server tags
What do the server tags on TEST COPY (update check) mean?
The game's server browser reads the tags TEST COPY (update check) publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does TEST COPY (update check) appear?
The Rust Server Trends lists that take in TEST COPY (update check) are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
How do you connect to TEST COPY (update check)?
You can connect by pressing F1 in Rust and typing client.connect 171.254.141.176:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.