StatusLive Servers online11,722 Players55,260 Populated3,387 Wiped · 3 h135 Interval5 min Date27 OCT 2026

DWG RG-S1575Server sheetchecked 10m ago

AFTER WORK | x1000

Online 46.8.197.95:28015 checked 10m ago

1000x weekly wipes moddedoxide
Connect
Players now 2/ 50 4% full
7-day average5peak 16
Rank#1,575top 7%
Last wipe5d agoweekly schedule
Next wipe1d 12hThu 29 Oct, 11:57 UTC
Fig. 1

Players

AveragePeak
0510152000:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Fig. 1Players on AFTER WORK | x1000
Fig. 2

Server performance

010020030040000:0009:0018:0004:0013:0022: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.

Fig. 2FPS, entities and memory
Fig. 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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

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

wipe-day peak11players, last three wipes

Coming wipes

  1. 1d 12hThu 29 Oct, 11:57 UTC
  2. 8d 19hThu 5 Nov, 19:00 UTCFW
  3. 15d 12hThu 12 Nov, 11:57 UTC
  4. 22d 12hThu 19 Nov, 11:57 UTC
  5. 29d 12hThu 26 Nov, 11:57 UTC
  6. 36d 19hThu 3 Dec, 19:00 UTCFW
  7. 43d 12hThu 10 Dec, 11:57 UTC

The first 48 hours of its last wipes

02.557.510+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
LuffyRust Texas USA - 1000x PvP NoBP Kits Skins Backpacks Noob NA · groups of 8+ · 1000x · weekly · 1 on average
2 / 50
02
Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 339 on average
224 / 300
03
TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPENA · groups of 8+ · 10x · weekly · 177 on average
251 / 300
04
Atlas - US 10x | No BPs | Kits | ShopNA · groups of 30+ · 10x · weekly · 177 on average
275 / 300
05
KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 148 on average
53 / 400
06
Vitality - US 10x | No BPs | Kits | ShopNA · groups of 32+ · 10x · weekly · 64 on average
26 / 50
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for AFTER WORK | x1000, and is it up?

Right now, AFTER WORK | x1000 is recorded as online. The uptime it reports puts the last restart at about 2 days 21 hours ago. For the last 4 full days the record is 96 of 96 hours up, 100% of the time. The first sighting of it by Rust Graphs was on 22 October 2026.

What does the recorded performance of AFTER WORK | x1000 show?

156 server fps on average over the last 48 hours, and never under 72. Counted at its highest: 88,682 entities, buildings, deployables and the rest of the world included. 4,161 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for AFTER WORK | x1000?

No region is published by AFTER WORK | x1000. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 46.8.197.95:28015.

On which Rust version is AFTER WORK | x1000 running?

Rust network protocol 2635 and build 168909 on Linux: that is what AFTER WORK | x1000 runs. The same protocol is required for joining, and Steam updates your game to it.

Counts

How many players are plotted on AFTER WORK | x1000?

2 of 50 slots on AFTER WORK | x1000 are taken at the latest refresh. Averaged across seven days, the player count is 5, with a peak of 16. Averaged over the last 48 hours, the player count is highest at 13:00 UTC: 15 players.

Against other Rust servers, where is AFTER WORK | x1000 placed?

Over the last seven days, AFTER WORK | x1000 records #1,575 for player hours: the top 7% of all ranked servers.

Schedules

What happens on AFTER WORK | x1000 on the day of a wipe?

The recent wipes averaged a busiest count of 11 players. At 47 hours after the latest wipe the crowd was at its peak.

On AFTER WORK | x1000, when do wipes occur?

Its tag is followed for the prediction: too few of AFTER WORK | x1000's wipes are on record to confirm the schedule. Thursday 29 October at 11:57 UTC is the date its next wipe is due. The world it runs now was made 5 days 11 hours ago. Its tags give a wipe schedule of one wipe a week.

Rules and settings

What settings and rules apply on AFTER WORK | x1000?

AFTER WORK | x1000 takes its gather rate from its name: 1000x. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.

On which map is AFTER WORK | x1000 played?

Seed 20261022 and size 3,500 define the procedural map AFTER WORK | x1000 generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does AFTER WORK | x1000 appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry AFTER WORK | x1000 are: Rust servers above 10x gather rate and Modded Rust servers. It is returned by these filters on the server list: 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.

On AFTER WORK | x1000, what is meant by each tag?

The game's server browser reads these tags from AFTER WORK | x1000: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): 50 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^w (Weekly): A wipe occurs every week; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Joining the server

How is AFTER WORK | x1000 joined?

Connect with client.connect 46.8.197.95:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players 50 player slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Wipe schedule

^w
Weekly A wipe occurs every week.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

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.

KeyTag string decoded