Station XX-15990 · no signal
PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1
Offline 180.149.231.164:28015 checked 21d ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,990
- top 71%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- 8d 15h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 15h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 8d 15hThu 5 Nov, 19:00 UTCFW
- 36d 15hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 20:18 UTC FW26d ago | M0.0■steady | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which settings and rules apply on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1?
Going by its name, PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 runs 2x gather. 100 players is the most a group can hold. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 right now?
A reading taken now finds PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 offline; the most recent activity was 21 days 11 hours ago.
How does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 rank against other Rust servers?
The last seven days of player hours place PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 at #15,990, in the top 71% of all ranked servers.
Server facts
How reliably does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 stay online?
As recorded now, PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 is not reachable, the last contact having been 21 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 23 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 run from?
Nothing about a region comes from PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 180.149.231.164:28015.
Which Rust version is PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 running?
PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 is running Rust network protocol 2634 and build 166494 on a machine with Windows. 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 2/1?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
How often does PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 wipe, and on which days?
Once a month PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 wipes, at the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 26 days 7 hours.
Lists and tags
What do the server tags on PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 mean?
Tags published by PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp20 (Max players): 20 slots are available; ts100 (Group limit): The team limit is 100; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): The game build is 166494; 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 2/1 appear?
You will find PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1 on the following Rust Server Trends lists: 2x Rust servers, listed live and 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; Gather rate: 2x.
Join the server
What steps get you onto PROJECT LAZARUS ORIGINAL | DayZ 2x | Weekly | Max 4 | Wiped 2/1?
To join, enter client.connect 180.149.231.164:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
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.