Procedural Map
Online 83.147.29.183:28025 checked 9m ago
Server instruments
last reading Wed 06:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 5 · below 20 is lag, below 10 is badEntities
48 h range 59,677–80,134 · memory 1,966 MBUptime
1 days 3 hours since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 32% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 38 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 06:07 UTC26d ago | 3 | – | running | 0 |
Peak: the most players in the first 48 hours. 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 wipes- 132/2000
- 108/2000
- 59/200
- 72/200
- 36/100
- 16/250
Quick answers
from the figures on this pageWipe timing
What happens on Procedural Map when wipe day comes?
The busiest point of its recent wipes drew 3 players on average. After the latest wipe, numbers topped out at 38 hours.
When does Procedural Map wipe?
Its rhythm cannot be told from the wipes of Procedural Map on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 26 days 1 hours ago.
Tags
How should you read the tags on Procedural Map?
Tags published by Procedural Map, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Procedural Map?
These Rust Metrics lists carry Procedural Map: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
Where does Procedural Map sit in the rankings?
Player hours over seven days put Procedural Map at #7,163, in the top 32% of all ranked servers.
What player count does Procedural Map carry?
0 of 100 slots are filled on Procedural Map right now. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 17:00 UTC, 1 players on average.
Server details
Where does Procedural Map sit?
No region comes from Procedural Map. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 83.147.29.183:28025.
What Rust version is Procedural Map on?
Version check: Rust network protocol 2635 and build 166652 on Windows, run by Procedural Map. Check: protocol. To join, your game must match; Steam handles the update.
How does Procedural Map perform?
Check: fps. Average 29 server fps over the last 48 hours, low of 5. Within range. Check: entities. The peak was 80,134, counting buildings, deployables and the rest of the world. Reading: 2,416 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
What is the uptime on Procedural Map, and is it online?
Procedural Map reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 27 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on Procedural Map?
Reading the name gives no gather rate for Procedural Map. 8 players per group, the default value. Mode check gives pve; fighting between players is off. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Procedural Map?
Size 3,700 and seed 657663029: the game generates the procedural map on Procedural Map from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
How do you connect to Procedural Map?
Press F1 in Rust and enter client.connect 83.147.29.183:28025. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.
