Rust Server TrendsSeismic network · station log
Recording Stations11,749 Players74,551 Active3,731 Wipes · 3 h142 48 h

Station XX-7172 · recording

Procedural Map

Online 83.147.29.183:28025 checked 12m ago

moddedoxidepve
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#7,172
top 32%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-7172 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Mon 16:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75114:0023:0008:0018:0003:0012:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

01020304014:0023:0008:0018:0003:0012: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 17 Sep. 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
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 32% 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
3players, 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 3, 38 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 06:07 UTC26d ago M0.5rising 3 – 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
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 246 on average
109/ 2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 236 on average
219/ 2000
Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 101 on average
36/ 200
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 59 on average
132/ 200
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 52 on average
61/ 100
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 52 on average
38/ 300
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Procedural Map?

The procedural map on Procedural Map is size 3,700 with seed 657663029, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Procedural Map?

No gather rate appears in the name of Procedural Map. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on Procedural Map?

At this moment, Procedural Map records 0 players across 100 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1. The busiest point in the last 48 hours came at 17:00 UTC, averaging 1 players.

How does Procedural Map rank against other Rust servers?

On player hours for the past week, Procedural Map sits at #7,172, which puts it inside the top 32% of every ranked server.

Server details

How reliably does Procedural Map stay online?

Right now, you can reach Procedural Map. Going by the uptime figure it reports, it restarted about 33 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does Procedural Map hold a steady tick rate?

Across the last 48 hours it averaged 29 server fps, with a floor of 5. Buildings, deployables and all the rest of the world's entities brought it to a high of 80,134. Memory use peaked at 2,416 MB. What you feel as lag is the combination of low fps and a rising entity count.

Which region does Procedural Map run from?

A region is not published by Procedural Map. 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 83.147.29.183:28025.

What build of Rust does Procedural Map use?

Procedural Map is running Rust network protocol 2635 and build 166652 on a machine with Windows. 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 Procedural Map?

3 players, on average, was the busiest crowd at its recent wipes. 38 hours after the latest wipe, the crowd peaked.

How often does Procedural Map wipe, and on which days?

The rhythm of Procedural Map 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. 26 days 7 hours is how long the current world has been running.

Server tags

What do the server tags on Procedural Map mean?

The game's server browser reads the tags Procedural Map publishes: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 Procedural Map appear?

You will find Procedural Map on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

What steps get you onto Procedural Map?

Enter client.connect 83.147.29.183:28025 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 mp100,ptrak,$r?,v2635,^p,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players 100 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs166652
Build Game build: 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's 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.

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.