On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 2
Rank#9,766top 44%
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
56/ 100
C−
Working its way up from the back of the class: #9,766 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
93/ 100
A
Mostly smooth: 56 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
57/ 100
C−
Moving up: up 1,351 places this week.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 44% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WWW·W
·······
···F·W·
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
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 UTCFW27d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The region code for INTFO Rust | Procedural is pol, but no region is published. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 91.240.74.124:28015.
How dependable is INTFO Rust | Procedural, and is it online at the moment?
Right now, INTFO Rust | Procedural is online. The uptime it reports puts the last restart at about 2 days 6 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
Is INTFO Rust | Procedural smooth to play on?
It never fell below 38 server fps in the last 48 hours, averaging 56. Buildings, deployables and everything else in the world added up to as many as 78,745 entities. At its highest, it used 3,985 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is INTFO Rust | Procedural running?
The server INTFO Rust | Procedural is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does INTFO Rust | Procedural wipe, and how often?
INTFO Rust | Procedural wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 25 days 20 hours.
What happens on INTFO Rust | Procedural when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 33 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 2.5 in the wipes where it did not hold.
Player numbers
Where does INTFO Rust | Procedural sit among Rust servers?
Over the last seven days, INTFO Rust | Procedural has #9,766 for player hours, in the top 44% of all ranked servers.
How many players does INTFO Rust | Procedural usually have?
Right now, 0 players are on INTFO Rust | Procedural, which has 10 slots. Averaging 0 players over seven days, it peaked at 2.
Tags
What is meant by the tags on INTFO Rust | Procedural?
The game's browser takes its cue from the tags INTFO Rust | Procedural has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $rpol (Region code): It is filed under the region code pol; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature INTFO Rust | Procedural?
Rust Server Score lists that include INTFO Rust | Procedural: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
How is INTFO Rust | Procedural set up, and what rules does it keep?
Nothing in the name of INTFO Rust | Procedural states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
INTFO Rust | Procedural runs which map?
The game generates the procedural map on INTFO Rust | Procedural at size 3,500 with seed 1573025114. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to INTFO Rust | Procedural?
To connect, start Rust, press F1, and type client.connect 91.240.74.124:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://rust.intfo.ru.
Server tags
what each one means
Published asmp10,ptrak,$rpol,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rpol
Region codeIt is filed under the region code pol.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).