Rust Data

rustdata.spaceservers40.160.241.203:28517.ipynb

Run all rust-data · live

‹ All servers

Offline NA · us2 40.160.241.203:28515 checked 15d ago

update-check

monthly wipes moddedcarbon

Connect

srv = rust.server("40.160.241.203:28517")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,352 # top 71% · #1545 in NA
last wipe 15d ago # monthly schedule
next wipe 7d 9h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 71% of all ranked servers, top 83% in NA. Ranked on player hours over the last seven days.

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h. # The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

inatkind
07d 9hThu 5 Nov, 19:00 UTCFW force wipe
135d 9hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 13 Oct, 14:36 UTC15d ago 0 NaN 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
40.160.241.203:28515
region
NA · us2
max players
100
group limit
8, the default
wipe schedule
monthly
last wipe
13 Oct 2026, 14:36 UTC
hostname
–
first seen
13 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[NA] Willjum's Casual Solo/Duo MonthlyNA · groups of 8+ · monthly · 15 on average2/175
1Hempville 420 No Kos Low Decay / Limited PvPNA · groups of 8+ · monthly · 7 on average6/90
2Made in Quebec & France! QC FR EN (Website 9 Languages)NA · groups of 8+ · monthly · 4 on average3/1000
3Testing GroundsNA · groups of 8+ · monthly · 2 on average0/15
4[US] Exile PvE | Noob Friendly | Raidable Bases | Skill Tree | NA · groups of 8+ · monthly · 1 on average0/50
5Apocrypha-Linux | PvE | PvPNA · groups of 20+ · monthly · 1 on average2/50

Quick answers

From the figures on this page.

Population

What position does update-check take in the server rankings?

Ranked #15,352 on seven-day player hours, update-check is #1,545 in North America and in the top 71% of all ranked servers.

What population does update-check carry?

Offline now for update-check, with the last sample 15 days 18 hours ago.

Server data

Which Rust version is update-check on?

The build is Rust network protocol 2634 and build 167781 on Linux, run by update-check. Steam updates your game for you, but the protocol must match to join.

How reliable is update-check, and is it online now?

update-check is offline at this refresh; the last response came 15 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 October 2026.

In which location is update-check hosted?

With its NA tag, update-check lists itself in North America; its region code is us2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 40.160.241.203:28515 is its address.

Map and rules

What rules and settings are recorded for update-check?

No gather rate appears in the name: update-check. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has update-check loaded?

The game generates its map: procedural, on update-check.

Wipe data

When does update-check wipe, and on what schedule?

Once a month update-check wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 15 days 19 hours ago. Its tags carry a monthly wipe schedule.

On update-check, what happens on wipe day?

Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Which lists on Rust Data hold update-check, and which filters?

These Rust Data lists include update-check: Modded Rust servers and North America Rust servers. It appears under these filters 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.

How should you read the server tags on update-check?

These tags are published by update-check and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $rus2 (Region code): us2 is the region code recorded; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon; NA (North America): The server browser files it under North America. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to update-check?

Enter client.connect 40.160.241.203:28515 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$rus2,v2634,^z,^y,^m,NA,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players 100 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Recorded game build: 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$rus2
Region code us2 is the region code recorded.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The plugin framework in use is Carbon.

Region

NA
North America The server browser files it under North America.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 51,425 players 11,685 servers online