StatusLive Servers online11,693 Players37,607 Populated2,934 Wiped · 3 h91 Interval5 min Date29 OCT 2026

DWG RG-S9772Server sheetchecked 10m ago

INTFO Rust | Procedural

Online 91.240.74.124:28015 checked 10m ago

moddedcarbon
Connect
Players now 0/ 10 0% full
7-day average0peak 2
Rank#9,772top 44%
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123403:0012:0021:0006:0015:0001:00

Hourly average and peak, UTC.

Fig. 1Players on INTFO Rust | Procedural
Fig. 2

Server performance

02040608003:0012:0021:0006:0015:0001: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 44% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.4 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2.5

The first 48 hours of its last wipes

Sat 3 OctThu 1 OctSun 20 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 08:19 UTC25d ago 2 – running 0
Thu 1 Oct, 22:32 UTC FW27d 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 UTC41d ago 1 – 0.6 days 0
Wed 16 Sep, 22:44 UTC42d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 155 on average
28 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
130 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average
31 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
14 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
3 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
2 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for INTFO Rust | Procedural, and is it up?

Right now, INTFO Rust | Procedural is recorded as online. About 2 days 4 hours ago is when it last restarted, measured from the uptime it reports. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 16 September 2026 is when Rust Graphs first saw it.

What does the recorded performance of INTFO Rust | Procedural show?

Average server fps over the last 48 hours is 56; the lowest was 38. Counted at its highest: 78,727 entities, buildings, deployables and the rest of the world included. 3,959 MB is the memory peak. A climbing entity count and low fps are the source of what players feel as lag.

In which location is INTFO Rust | Procedural hosted?

A region code of pol is published, but no region, by INTFO Rust | Procedural. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 91.240.74.124:28015.

On which Rust version is INTFO Rust | Procedural running?

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on INTFO Rust | Procedural. The same protocol is required for joining, and Steam updates your game to it.

Counts

What player count is recorded on INTFO Rust | Procedural?

Current player count on INTFO Rust | Procedural: 0, of 10 slots. The seven-day mean is 0 players; the peak over the same period is 2.

Against other Rust servers, where is INTFO Rust | Procedural placed?

Player hours over seven days place INTFO Rust | Procedural at #9,772, within the top 44% of ranked servers.

Wipe data

What is recorded on INTFO Rust | Procedural on wipe day?

An average of 1 players was recorded at the busiest point of its recent wipes. 33 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 2.5.

What wipe schedule has been recorded for INTFO Rust | Procedural?

No next wipe can be predicted for INTFO Rust | Procedural: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 25 days 18 hours ago.

Map and rules

Which rules and settings are recorded for INTFO Rust | Procedural?

No gather rate is stated in the name of INTFO Rust | Procedural. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Carbon. Anti-cheat: VAC, from Valve, is on.

Which map has INTFO Rust | Procedural loaded?

Seed 1573025114 and size 3,500 define the procedural map INTFO Rust | Procedural generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

Where does INTFO Rust | Procedural appear among the Rust Graphs lists and filters?

On Rust Graphs, INTFO Rust | Procedural is placed in these lists: Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

On INTFO Rust | Procedural, what is meant by each tag?

Tags published by INTFO Rust | Procedural, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $rpol (Region code): Region code: pol; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Plugin framework: Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Joining the server

By what method do you join INTFO Rust | Procedural?

In Rust, press F1 and type client.connect 91.240.74.124:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://rust.intfo.ru is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp10,ptrak,$rpol,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust style.
mp10
Max players The slot count is 10.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$rpol
Region code Region code: pol.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon Plugin framework: Carbon.

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.

KeyTag string decoded