Rust Data

rustdata.spaceservers157.85.91.86:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 157.85.91.86:28015 checked 8d ago

Punch The Clock | Casual Vanilla for Busy People

moddedoxide

Connect

srv = rust.server("157.85.91.86:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 2/75 # 3% full
7-day average 0 # peak –
rank #11,510 # top 52%
last wipe 9d ago # no schedule published
next wipe – # too few wipes seen yet

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, measured since 18 Oct. 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
15k10k15k20k18 Oct20 Oct21 Oct23 Oct24 Oct26 Oct

Top 52% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 18 Oct, 17:39 UTC9d ago 2 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

3000 · seed 50000
Map of Punch The Clock | Casual Vanilla for Busy People
map
Procedural Map
size
3000
seed
50000
Open on RustMaps

Server

srv.info()
address
157.85.91.86:28015
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 17:39 UTC
hostname
–
first seen
18 Oct 2026

About this server · in its own words

print(srv.description)
Chill offline protection(when i figure it out) new to starting a server Server restart 12am and 12pm ADT

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average143/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average139/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average28/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average124/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average43/1000

Quick answers

From the figures on this page.

Population

How does Punch The Clock | Casual Vanilla for Busy People compare in the rankings?

Over the last seven days Punch The Clock | Casual Vanilla for Busy People sits at #11,510 on player hours, in the top 52% of ranked servers.

How full does Punch The Clock | Casual Vanilla for Busy People run?

The current row shows Punch The Clock | Casual Vanilla for Busy People offline; the last response was 8 days 17 hours ago.

Server data

What is the Rust version on Punch The Clock | Casual Vanilla for Busy People?

Rust network protocol 2634 and build 167781 on Linux is what Punch The Clock | Casual Vanilla for Busy People runs. Joining needs the same protocol on your game; Steam handles the update.

Is Punch The Clock | Casual Vanilla for Busy People up, and what does its uptime show?

The latest sample has Punch The Clock | Casual Vanilla for Busy People offline, with a last sighting 8 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 18 October 2026.

In which location is Punch The Clock | Casual Vanilla for Busy People hosted?

For Punch The Clock | Casual Vanilla for Busy People, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.91.86:28015 is its address.

Map and rules

What rules and settings are recorded for Punch The Clock | Casual Vanilla for Busy People?

No gather rate appears in the name: Punch The Clock | Casual Vanilla for Busy People. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on Punch The Clock | Casual Vanilla for Busy People?

The game generates the map on Punch The Clock | Casual Vanilla for Busy People: procedural, size 3,000, seed 50000. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

On what schedule does Punch The Clock | Casual Vanilla for Busy People wipe?

Too few wipes are on record for Punch The Clock | Casual Vanilla for Busy People to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 9 days 3 hours ago.

On Punch The Clock | Casual Vanilla for Busy People, what happens on wipe day?

Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 6 hours after it began.

Lists and tags

Where does Punch The Clock | Casual Vanilla for Busy People appear among Rust Data lists and filters?

On Rust Data, Punch The Clock | Casual Vanilla for Busy People appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on Punch The Clock | Casual Vanilla for Busy People?

The game's server browser reads these tags from Punch The Clock | Casual Vanilla for Busy People: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to Punch The Clock | Casual Vanilla for Busy People?

The manual route: launch Rust, F1, then client.connect 157.85.91.86:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp75,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp75
Max players Slot count: 75.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Build number: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 77,057 players 11,838 servers online