Rust Server TrendsSeismic network · station log
Recording Stations11,736 Players50,841 Active3,279 Wipes · 3 h115 48 h

Station XX-14102 · no signal

Taskmaster's Server DO NOT JOIN

Offline 70.176.29.126:28015 checked 13d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,102
top 65%
Last wipe
15d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14102 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k13 Oct15 Oct17 Oct18 Oct20 Oct22 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 13 Oct, 08:01 UTC15d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 156 on average
46/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
124/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
45/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 92 on average
50/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
9/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
6/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Taskmaster's Server DO NOT JOIN?

Taskmaster's Server DO NOT JOIN uses a procedural map, which the game generates.

Which settings and rules apply on Taskmaster's Server DO NOT JOIN?

No gather rate appears in the name of Taskmaster's Server DO NOT JOIN. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched off.

Population

How many players are recorded on Taskmaster's Server DO NOT JOIN right now?

No players are recorded on Taskmaster's Server DO NOT JOIN at this moment; it is offline, and the last sighting was 13 days 18 hours ago.

How does Taskmaster's Server DO NOT JOIN rank against other Rust servers?

The last seven days of player hours place Taskmaster's Server DO NOT JOIN at #14,102, in the top 65% of all ranked servers.

Server details

How reliably does Taskmaster's Server DO NOT JOIN stay online?

As recorded now, Taskmaster's Server DO NOT JOIN is not reachable, the last contact having been 13 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.

Which region does Taskmaster's Server DO NOT JOIN run from?

Nothing about a region comes from Taskmaster's Server DO NOT JOIN. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 70.176.29.126:28015.

Which Rust version is Taskmaster's Server DO NOT JOIN running?

Rust network protocol 2634 and build 167584 on Windows is what Taskmaster's Server DO NOT JOIN runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Taskmaster's Server DO NOT JOIN?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does Taskmaster's Server DO NOT JOIN wipe, and on which days?

The rhythm of Taskmaster's Server DO NOT JOIN cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 15 days 16 hours.

Tags

What do the server tags on Taskmaster's Server DO NOT JOIN mean?

The game's server browser reads the tags Taskmaster's Server DO NOT JOIN publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167584 (Build): It runs game build 167584; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Taskmaster's Server DO NOT JOIN appear?

You will find Taskmaster's Server DO NOT JOIN on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Taskmaster's Server DO NOT JOIN?

You can connect by pressing F1 in Rust and typing client.connect 70.176.29.126:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167584
Build It runs game build 167584.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.