RUST METRICSFlight deck · live data
Data live Servers11,853 Players81,845 Populated3,922 Fresh wipes 3 h169 Scan5 min
‹ All servers46.8.197.95:28015
Online Full Queue Fresh wipe Wipe due No query

AFTER WORK | x1000

Online 46.8.197.95:28015 checked 10m ago

1000x weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Tue 19:00 UTC
0 12 25 38 50 PAX 6 /50

Players now

12% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 88 SERVER FPS

Server fps

48 h low 72 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 83,907 ×1000

Entities

48 h range 81,070–88,682 · memory 3,940 MB
1239 ET SINCE RESTART 2D 18H

Uptime

2 days 18 hours since its last restart, at the last reading
7-day average5peak 16
Rank#1,598top 7%
Last wipe5d agoweekly schedule
Next wipe1d 15hThu 29 Oct, 11:57 UTC
Memory3,940MB48 h peak 16 players
REC 1

Players

AveragePeak
0510152021:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040021:0006:0015:0001:0010:0019:00

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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k22 Oct23 Oct24 Oct25 Oct26 Oct27 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 11:57 UTC, in 1d 15h. Its weekly schedule tag · low confidence

wipe-day peak11players, last three wipes

Coming wipes

  1. WPT 1Thu 29 Oct, 11:57 UTC1d 15h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 22hFW
  3. WPT 3Thu 12 Nov, 11:57 UTC15d 15h
  4. WPT 4Thu 19 Nov, 11:57 UTC22d 15h
  5. WPT 5Thu 26 Nov, 11:57 UTC29d 15h
  6. WPT 6Thu 3 Dec, 19:00 UTC36d 22hFW
  7. WPT 7Thu 10 Dec, 11:57 UTC43d 15h

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 11:57 UTC5d ago 11 – running 1

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on AFTER WORK | x1000 when wipe day comes?

An average of 11 players came at the busiest on its recent wipes. 47 hours after the wipe, the crowd peaked on the latest wipe.

When does AFTER WORK | x1000 wipe?

Its tag guides the prediction: too few of AFTER WORK | x1000's wipes are on record to confirm its schedule. Thursday 29 October at 11:57 UTC is when its next wipe is due. 5 days 8 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.

Lists and filters

Which tags does AFTER WORK | x1000 carry, and what do they mean?

Tags published by AFTER WORK | x1000, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^w (Weekly): It wipes each week; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show AFTER WORK | x1000?

On Rust Metrics, AFTER WORK | x1000 sits in these lists: Gather rate above 10x: server list and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: More than 10x.

Player count

Where does AFTER WORK | x1000 sit in the rankings?

Ranking for AFTER WORK | x1000: #1,598 on seven-day player hours, top 7% of all ranked servers.

What player count does AFTER WORK | x1000 carry?

Current headcount on AFTER WORK | x1000: 6 players, 50 slots available. Check: players over seven days. Average 5, peak 16. The last 48 hours peaked at 13:00 UTC, averaging 15 players at that hour.

Server details

Which location does AFTER WORK | x1000 run from?

No region tag on AFTER WORK | x1000. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.8.197.95:28015.

What Rust version is AFTER WORK | x1000 on?

Reading: AFTER WORK | x1000, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for AFTER WORK | x1000?

Check: fps. Average 159 server fps over the last 48 hours, low of 72. Within range. Reading: 88,682 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,161 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on AFTER WORK | x1000, and is it online?

Check: connection. AFTER WORK | x1000 is online at this moment. Check: restart. The uptime it reports puts the last restart about 2 days 18 hours ago. Uptime for the last 4 full days: 96 of 96 hours, or 100%. The first sighting on Rust Metrics was 22 October 2026.

Map and rules

How is AFTER WORK | x1000 configured, and what rules are in force?

The name carries the rate: 1000x gather on AFTER WORK | x1000. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on AFTER WORK | x1000?

Check: map. Procedural, size 3,500, seed 20261022, generated by the game on AFTER WORK | x1000. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How do you connect to AFTER WORK | x1000?

Press F1 in Rust and enter client.connect 46.8.197.95:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes each week.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.