Offline 85.27.20.40:28015 checked 31d ago
Projet Automatisation
Connect
srv = rust.server("85.27.20.40:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 85.27.20.40:28015
- region
- –
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 16:20 UTC
- hostname
- –
- first seen
- 26 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 181/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 89 on average | 144/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 20/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 45/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Projet Automatisation rank?
Player hours over seven days put Projet Automatisation at #15,725, in the top 67% of the ranked set.
What population does Projet Automatisation carry?
Projet Automatisation returns no live count at this refresh, having last been seen 31 days 21 hours ago.
Server data
Which Rust version is Projet Automatisation on?
Rust network protocol 2633 and build 165217 on Windows is what Projet Automatisation runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Projet Automatisation, and is it online now?
The latest sample has Projet Automatisation offline, with a last sighting 31 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 26 September 2026.
Which location does Projet Automatisation run from?
There is no region published for Projet Automatisation. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 85.27.20.40:28015.
Map and rules
Which settings and rules does Projet Automatisation run?
You will not find a gather rate in the string Projet Automatisation. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Projet Automatisation loaded?
The game generates its map: procedural, on Projet Automatisation.
Wipe schedule
When does Projet Automatisation wipe, and on what schedule?
Too few wipes are on record for Projet Automatisation to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 31 days 22 hours ago, and that is the one in play.
Tags and filters
Where does Projet Automatisation appear among Rust Data lists and filters?
The Rust Data lists that Projet Automatisation fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Projet Automatisation?
The game's server browser reads these tags from Projet Automatisation: gmrust (Game mode): Survival play, standard Rust; mp250 (Max players): Slot count: 250; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Projet Automatisation?
In Rust, F1 opens the console: type client.connect 85.27.20.40:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.