Station US-15454 · no signal
update-check
Offline NA · us2 51.81.167.73:28515 checked 2d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70% · #1535 in NA
- Last wipe
- 2d ago
- monthly schedule
- Next wipe
- 12d 6h
- Thu 3 Dec, 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 70% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 3 December, 19:00 UTC, in 12d 6h. The force wipe · high confidence
- usual gap
- 1 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 12d 6hThu 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 |
|---|---|---|---|---|---|---|
| Thu 19 Nov, 08:03 UTC2d ago | M0.0■steady | 0 | – | – | running | 0 |
| Wed 18 Nov, 08:09 UTC3d ago | M0.0■steady | 0 | – | 1 days | 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?
The map on update-check is procedural, produced by the game.
Which settings and rules apply on update-check?
The name of update-check gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. 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?
A reading taken now finds update-check offline; the most recent activity was 2 days 4 hours ago. The population averaged 0 players over the past week.
How does update-check rank against other Rust servers?
update-check is #1,535 in North America and #15,454 worldwide on the past week's player hours, within the top 70% of ranked servers.
Server facts
How reliably does update-check stay online?
As recorded now, update-check is not reachable, the last contact having been 2 days 4 hours ago. 2 of 168 hours in the last 7 full days were up time, 1% of the total. On 5 November 2026 it was recorded for the first time by Rust Server Trends.
Which region does update-check run from?
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. The address it publishes is 51.81.167.73:28515.
Which Rust version is update-check running?
On Linux, update-check runs Rust network protocol 2636 and build 127089. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on update-check?
On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.
How often does update-check wipe, and on which days?
At the force wipe each month update-check wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 3 December at 19:00 UTC, it takes its next wipe. 2 days 4 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?
Tags published by update-check and read by the game's server browser include 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; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs127089-84fd9a97663 (Build): You won't find a published build number; ptrak (Networking): The network layer is RakNet, the game's standard; $rus2 (Region code): Region code: us2; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here; NA (North America): The server browser files it under North America. 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 update-check appear?
You will find update-check on the following Rust Server Trends lists: Modded Rust servers, tracked live and North America Rust servers. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.
How to join
How do you connect to update-check?
Enter client.connect 51.81.167.73:28515 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.