INTFO Rust | Procedural
Online 91.240.74.124:28015 checked 1h ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 29 · below 20 is lag, below 10 is badEntities
48 h range 76,170–79,806 · memory 3,745 MBUptime
1 days 19 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 44% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 2, 33 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 08:19 UTC25d ago | 2 | – | running | 0 |
| Thu 1 Oct, 22:32 UTC FW26d ago | 1 | – | 1.4 days | 0 |
| Sun 20 Sep, 11:26 UTC38d ago | 1 | halved by day 4 | 11.5 days | 0 |
| Fri 18 Sep, 11:05 UTC40d ago | 1 | halved by day 1 | 2 days | 0 |
| Thu 17 Sep, 20:42 UTC40d ago | 1 | – | 0.6 days | 0 |
| Wed 16 Sep, 22:44 UTC41d ago | 1 | – | 0.9 days | 1 |
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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on INTFO Rust | Procedural?
An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 33 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2.5 it fell below half when it didn't.
How often does INTFO Rust | Procedural wipe, and when?
No next wipe can be predicted for INTFO Rust | Procedural, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 25 days 9 hours ago.
Tag meanings
How should you read the tags on INTFO Rust | Procedural?
These are the tags INTFO Rust | Procedural publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $rpol (Region code): pol is the region code on record; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show INTFO Rust | Procedural?
These Rust Metrics lists carry INTFO Rust | Procedural: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Occupancy
Where does INTFO Rust | Procedural sit in the rankings?
Ranking for INTFO Rust | Procedural: #9,810 on seven-day player hours, top 44% of all ranked servers.
What player count does INTFO Rust | Procedural carry?
0 of 10 slots are filled on INTFO Rust | Procedural right now. Seven-day check: 0 players on average. Peak reading: 2. Check: 48-hour peak. 22:00 UTC, 2 players on average.
Operator and location
Where does INTFO Rust | Procedural sit?
No region tag on INTFO Rust | Procedural, whose region code is pol. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 91.240.74.124:28015.
What Rust version is INTFO Rust | Procedural on?
Reading: INTFO Rust | Procedural, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
Is performance on INTFO Rust | Procedural within range?
Reading: 56 server fps on average across the last 48 hours. It never dropped below 29. Check: entities. The peak was 79,806, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 5,031 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is INTFO Rust | Procedural, and is it online now?
Reading: online. INTFO Rust | Procedural answers right now. Reading: uptime. About 43 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 16 September 2026, recorded by Rust Metrics.
Rules and settings
How is INTFO Rust | Procedural configured, and what rules are in force?
Check: gather rate. The name INTFO Rust | Procedural does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.
What map is INTFO Rust | Procedural on?
Check: map. Procedural, size 3,500, seed 1573025114, generated by the game on INTFO Rust | Procedural. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How do you connect to INTFO Rust | Procedural?
Check: join. Open Rust, press F1, then enter client.connect 91.240.74.124:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://rust.intfo.ru.