Rust Server TrendsSeismic network · station log
Recording Stations11,767 Players60,429 Active3,522 Wipes · 3 h133 48 h

Station XX-16006 · no signal

lorezone

Offline 69.207.157.156:28015 checked 26d ago

Connect
Players now
0/ 2
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,006
top 69%
Last wipe
29d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16006 · 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 2 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
15k10k15k20k29 Sep1 Oct3 Oct4 Oct6 Oct8 Oct

Top 69% 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
2players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 16:32 UTC29d ago M0.3rising 2 – 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 554 on average
416/ 500
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
277/ 300
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 295 on average
42/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 294 on average
35/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 273 on average
75/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 252 on average
94/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on lorezone?

The map on lorezone is procedural, produced by the game.

Which settings and rules apply on lorezone?

No gather rate appears in the name of lorezone. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. Anti-cheat is on: VAC, from Valve.

Player counts

What is the current population on lorezone?

No players are recorded on lorezone at this moment; it is offline, and the last sighting was 26 days 23 hours ago.

How does lorezone rank against other Rust servers?

Over the last seven days, lorezone recorded enough player hours to reach #16,006 worldwide, placing it in the top 69% of all ranked servers.

Operator and location

How reliably does lorezone stay online?

As recorded now, lorezone is not reachable, the last contact having been 26 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 29 September 2026.

Which region does lorezone run from?

No region is published by lorezone. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 69.207.157.156:28015.

Which Rust version is lorezone running?

On Windows, lorezone runs Rust network protocol 2633 and build 165217. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on lorezone?

The recent wipes averaged a busiest count of 2 players. 3 hours into the latest wipe, the crowd reached its peak.

How often does lorezone wipe, and on which days?

The rhythm of lorezone cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 29 days 5 hours.

Server tags

What do the server tags on lorezone mean?

These are the tags lorezone publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp2 (Max players): 2 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. 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 lorezone appear?

You will find lorezone on the following Rust Server Trends lists: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

How do you connect to lorezone?

Enter client.connect 69.207.157.156: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 mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp2
Max players 2 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build The game build is 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

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.