Offline EU 185.248.103.222:32015 checked 8h ago
Turbo [TRIO | X4 | KIT | TP] 24.10
Connect
srv = rust.server("185.248.103.222:32016")
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, measured since 17 Oct. 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 15% of all ranked servers, top 43% in EU. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 09:51 UTC, in 3d 4h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 3d 4h | Sat 31 Oct, 09:51 UTC | wipe |
| 1 | 8d 13h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 10d 4h | Sat 7 Nov, 09:51 UTC | wipe |
| 3 | 17d 4h | Sat 14 Nov, 09:51 UTC | wipe |
| 4 | 24d 4h | Sat 21 Nov, 09:51 UTC | wipe |
| 5 | 31d 4h | Sat 28 Nov, 09:51 UTC | wipe |
| 6 | 36d 13h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 38d 4h | Sat 5 Dec, 09:51 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 34 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 09:51 UTC3d ago | 2 | NaN | running | 1 |
| 1 | Fri 23 Oct, 04:33 UTC5d ago | 1 | NaN | 1.2 days | 1 |
| 2 | Wed 21 Oct, 07:35 UTC6d ago | 1 | NaN | 1.9 days | 1 |
| 3 | Tue 20 Oct, 08:51 UTC7d ago | 1 | NaN | 0.9 days | 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.
display(srv.map, srv.info())Map
1000 · seed 14580![Map of Turbo [TRIO | X4 | KIT | TP] 24.10](https://files.facepunch.com/rust/map-images/32dde0c9cc424a290235efd550970f09bc04738742c5274b191502f85c098ebe/proceduralmap.1000.0.289_32dde0c9cc424a290235efd550970f09.jpg)
- map
- Procedural Map
- size
- 1000
- seed
- 14580
Server
srv.info()- address
- 185.248.103.222:32015
- region
- EU
- max players
- 250
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 24 Oct 2026, 09:51 UTC
- hostname
- –
- first seen
- 17 Oct 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [RU] Восход [TRIO| X4 | KIT] 24.10 | EU · groups of 8+ · 4x · weekly · 1 on average | 1/300 |
| 1 | Atlas - EU 3x | No BPs | Mondays | EU · groups of 16+ · 3x · weekly · 389 on average | 252/300 |
| 2 | Magic Rust #18 — Vanilla 2x | Pyccкий | EU · groups of 150+ · 2x · weekly · 323 on average | 13/100 |
| 3 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 298 on average | 89/1000 |
| 4 | MIRAGE RUST | MAIN 2x | VANILLA+ | Wipe 23.10 | EU · groups of 300+ · 2x · weekly · 266 on average | 22/500 |
| 5 | Magic Rust #14 — Modded 2x (No limit) | Pyccкий | EU · groups of 300+ · 2x · weekly · 264 on average | 88/110 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Turbo [TRIO | X4 | KIT | TP] 24.10 rank?
Player hours over the last seven days: #3,331 for Turbo [TRIO | X4 | KIT | TP] 24.10, #1,251 in Europe, within the top 15% of the ranked set.
How full does Turbo [TRIO | X4 | KIT | TP] 24.10 run?
Turbo [TRIO | X4 | KIT | TP] 24.10 returns no live count at this refresh, having last been seen 8 hours ago. Over the last seven days it averaged 1 players and peaked at 2. Peak hour in the last 48 hours: 10:00 UTC, mean 1 players.
Server data
How well does Turbo [TRIO | X4 | KIT | TP] 24.10 perform?
Server fps over the last 48 hours averages 217; the floor is 165. The entity count peaked at 3,677, covering buildings, deployables and the rest of the world. The memory field tops out at 925 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is Turbo [TRIO | X4 | KIT | TP] 24.10 on?
Rust network protocol 2635 and build 168909 on Linux is what Turbo [TRIO | X4 | KIT | TP] 24.10 runs. Steam updates your game for you, but the protocol must match to join.
Is Turbo [TRIO | X4 | KIT | TP] 24.10 up, and what does its uptime show?
Turbo [TRIO | X4 | KIT | TP] 24.10 is offline at this refresh; the last response came 8 hours ago. The uptime it reports puts the last restart about 3 days 10 hours ago. Uptime of 98% across the last 7 full days: 165 hours of 168. Its earliest recorded date in Rust Data is 17 October 2026.
Which location does Turbo [TRIO | X4 | KIT | TP] 24.10 run from?
With its EU tag, Turbo [TRIO | X4 | KIT | TP] 24.10 lists itself in Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 185.248.103.222:32015.
Map and rules
Which settings and rules does Turbo [TRIO | X4 | KIT | TP] 24.10 run?
4x gather is what the name states, and the name is Turbo [TRIO | X4 | KIT | TP] 24.10. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on Turbo [TRIO | X4 | KIT | TP] 24.10?
The game generates the map on Turbo [TRIO | X4 | KIT | TP] 24.10: procedural, size 1,000, seed 14580. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Turbo [TRIO | X4 | KIT | TP] 24.10 wipe, and on what schedule?
Too few wipes are on record for Turbo [TRIO | X4 | KIT | TP] 24.10 to confirm its schedule, so the tag drives the prediction. Saturday 31 October at 09:51 UTC is when the next wipe is due. A new world was started 3 days 19 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.
On Turbo [TRIO | X4 | KIT | TP] 24.10, what happens on wipe day?
The average peak over recent wipes is 1 players. 34 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain Turbo [TRIO | X4 | KIT | TP] 24.10?
The Rust Data lists that Turbo [TRIO | X4 | KIT | TP] 24.10 fits are: EU Rust servers, Modded Rust servers and Rust tutorial servers. Under these filters on the server list, it is listed: Region: Europe; Type: Modded; Server tag: Weekly ^w, Tutorial on ^t, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.
How should you read the server tags on Turbo [TRIO | X4 | KIT | TP] 24.10?
These tags are published by Turbo [TRIO | X4 | KIT | TP] 24.10 and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp250 (Max players): Slot count: 250; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^t (Tutorial on): Start here with Facepunch's tutorial if you are new; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EU (Europe): The server browser files it under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to Turbo [TRIO | X4 | KIT | TP] 24.10?
Enter client.connect 185.248.103.222:32015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.