update-check
Offline NA · us2 40.160.241.203:28515 checked 15d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 12h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 13 Oct, 14:36 UTC15d ago | 0 | – | running | 0 |
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| Server | Profile | Players now |
|---|---|---|
| [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 15 on average | 10 / 175 |
| Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 7 / 90 |
| Made in Quebec & France! QC FR EN (Website 9 Languages) | NA · groups of 8+ · monthly · 4 on average | 3 / 1000 |
| Testing Grounds | NA · groups of 8+ · monthly · 2 on average | 0 / 15 |
| [US] Exile PvE | Noob Friendly | Raidable Bases | Skill Tree | | NA · groups of 8+ · monthly · 1 on average | 0 / 50 |
| Apocrypha-Linux | PvE | PvP | NA · groups of 20+ · monthly · 1 on average | 1 / 50 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for update-check: what is it?
The force wipe is the only wipe for update-check, once a month. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. 15 days 15 hours ago the current world was made. The tags carry a monthly wipe schedule.
Wipe day on update-check: what should you expect?
The average busiest count over recent wipes is 0 players. The highest player count on the latest wipe arrived 0 hours in.
Server details
In which region does update-check sit?
In North America, by its NA tag, sits update-check; the region code is us2. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 40.160.241.203:28515 is its address.
Which Rust version is update-check on?
On Linux, update-check runs Rust network protocol 2634 and build 167781. Joining requires the same protocol on your game; Steam handles the update.
Is update-check up, and how steady is its uptime?
Offline at this refresh: update-check, last seen 15 days 15 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 October 2026.
Lists and tags
What do update-check's tags stand for?
gmrust (Game mode): Rust survival, standard ruleset; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): To join, your game version must match protocol 2634; cs167781 (Build): Build number 167781; ptrak (Networking): RakNet is the network layer, the game's standard one; $rus2 (Region code): us2 is the region code on record; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^z (Modded): Modded listing, where plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; NA (North America): The server browser files it under North America are the tags update-check publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does update-check appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists update-check fits are: Modded Rust servers: live data 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.
Player numbers
Against other Rust servers, how does update-check compare?
update-check holds #15,352 on seven-day player hours and #1,545 in North America, inside the top 71% of the ranked field.
At what level does update-check run its population?
update-check is offline at this refresh; the last contact was 15 days 15 hours ago.
Map and rules
What are the settings on update-check, and its rules?
The name of update-check does not state a gather rate. The default group cap of 8 players applies. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map for update-check?
The game generates a procedural map for update-check.
Connection
How can a player join update-check?
In the Rust console (F1), enter client.connect 40.160.241.203:28515. Launch Rust on this page also works, opening Rust through Steam and connecting you.