Rust Server TrendsSeismic network · station log
Recording Stations11,750 Players59,433 Active3,457 Wipes · 3 h133 48 h

Station XX-16837 · no signal

PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/

Offline 1.42.229.18:28015 checked 27d ago

2x moddedoxide
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,837
top 71%
Last wipe
33d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16837 · 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 20 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
15k10k15k20k20 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

Top 71% 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
0players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 26 Sep, 09:04 UTC31d ago M0.0steady 0 – 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
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 714 on average
499/ 650
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 535 on average
348/ 425
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 345 on average
227/ 250
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 322 on average
10/ 100
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 320 on average
182/ 230
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 295 on average
189/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/?

Its name points to a gather rate of 2x on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/. 100 players is the most a group can hold. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/?

A reading taken now finds PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ offline; the most recent activity was 27 days 21 hours ago.

How does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ rank against other Rust servers?

The last seven days of player hours place PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ at #16,837, in the top 71% of all ranked servers.

Operator and location

How reliably does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ stay online?

No contact with PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ right now, and the last recorded contact was 27 days 21 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Where in the world is PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ hosted?

A region is not published by PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 1.42.229.18:28015.

What build of Rust does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ use?

On Windows, PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/?

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

On what timetable does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ run its wipes?

Too few wipes of PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 33 days 4 hours.

Tags

What do the server tags on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ mean?

The game's server browser reads the tags PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ publishes: gmrust (Game mode): You'll find standard Rust survival here; mp20 (Max players): 20 slots are available; ts100 (Group limit): Each team can hold up to 100; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ appear?

You will find PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/ on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

Connecting

What steps get you onto PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 25/?

Enter client.connect 1.42.229.18:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2633,gmrust,cs165217,ts100,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp20
Max players 20 slots are available.
ts100
Group limit Each team can hold up to 100.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build The game build is 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.