Station US-15352 · no signal
update-check
Offline NA · us2 40.160.241.203:28515 checked 15d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,352
- top 71% · #1545 in NA
- Last wipe
- 15d ago
- monthly schedule
- Next wipe
- 7d 11h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 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 71% of all ranked servers, top 83% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 11hThu 5 Nov, 19:00 UTCFW
- 35d 11hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 13 Oct, 14:36 UTC15d ago | M0.0■steady | 0 | – | – | running | 0 |
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 pageMap and rules
Which map is running on update-check?
A procedural map runs on update-check, generated by the game.
Which settings and rules apply on update-check?
The name of update-check gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on update-check right now?
update-check is not responding at this moment and is offline, last seen 15 days 16 hours ago.
How does update-check rank against other Rust servers?
For player hours across the last seven days, update-check takes #15,352 overall and #1,545 in North America, inside the top 71% of all ranked servers.
Server facts
How reliably does update-check stay online?
As recorded now, update-check is not reachable, the last contact having been 15 days 16 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 13 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is update-check hosted?
The NA tag puts update-check in North America, and the region code it publishes is us2. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 40.160.241.203:28515 is the address it uses.
What build of Rust does update-check use?
update-check is running Rust network protocol 2634 and build 167781 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on update-check?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
How often does update-check wipe, and on which days?
Once a month update-check wipes, at the force wipe. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 15 days 16 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Tags
What do the server tags on update-check mean?
These are the tags update-check publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $rus2 (Region code): Region code: us2; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here; NA (North America): The server browser files it under North America. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does update-check appear?
These Rust Server Trends lists include update-check: Modded Rust servers, tracked live and North America Rust servers. On the server list, the filters it matches are: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Join the server
How do you connect to update-check?
To join, enter client.connect 40.160.241.203:28515 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.