Online 135.148.15.102:23565 checked 12m ago
1000x | Cross Rust | Weekly
Connect
srv = rust.server("135.148.15.102:23566")
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 28 Sep. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 6 Oct, 21:38 UTC22d ago | 1 | NaN | running | 0 |
| 1 | Mon 5 Oct, 22:46 UTC23d ago | 1 | NaN | 1 days | 0 |
| 2 | Mon 28 Sep, 01:10 UTC31d ago | 2 | halved by day 3 | 7.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
3000 · seed 1218474365
- map
- Procedural Map
- size
- 3000
- seed
- 1218474365
Server
srv.info()- address
- 135.148.15.102:23565
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 21:45 UTC
- hostname
- –
- first seen
- 28 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 | AfterWork | x1000 | RU | EU · groups of 8+ · 1000x · weekly · 5 on average | 5/50 |
| 1 | PARADISE RUST #1 [ X1000 | BATTLEFILD | NOLIMIT | KITS | PVP ] | groups of 36+ · 1000x · 3 on average | 4/250 |
| 2 | The Darkest Valley | 1000X | BI-WEEKLY| NO VIP | RAIDABLE BASES | groups of 8+ · 1000x · 2 on average | 1/50 |
| 3 | [US] World War Rust | X1000 | Loot++ | Monthly Wipe | NA · groups of 8+ · 1000x · monthly · 2 on average | 3/100 |
| 4 | Demonic Rust |№2|X1000|PVP|TP|DRONES|FPS+ | groups of 50+ · 1000x · 2 on average | 0/90 |
| 5 | [DE] Battlearena x1000 #Kit #Zombies and more ... | groups of 8+ · 1000x · 1 on average | 0/16 |
Quick answers
From the figures on this page.
Population
How does 1000x | Cross Rust | Weekly compare in the rankings?
Player hours over seven days put 1000x | Cross Rust | Weekly at #15,289, in the top 69% of the ranked set.
What population does 1000x | Cross Rust | Weekly carry?
1000x | Cross Rust | Weekly reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on 1000x | Cross Rust | Weekly?
Averaged over 48 hours: 199 server fps, never under 120. Entity numbers reached 47,272, and that includes buildings, deployables and the rest. The memory field tops out at 3,820 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is 1000x | Cross Rust | Weekly on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by 1000x | Cross Rust | Weekly. Joining needs the same protocol on your game; Steam handles the update.
Is 1000x | Cross Rust | Weekly up, and what does its uptime show?
The current sample puts 1000x | Cross Rust | Weekly online. Count back 2 days 10 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 28 September 2026.
In which location is 1000x | Cross Rust | Weekly hosted?
There is no region published for 1000x | Cross Rust | Weekly. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 135.148.15.102:23565.
Map and rules
Which settings and rules does 1000x | Cross Rust | Weekly run?
1000x gather is what the name states, and the name is 1000x | Cross Rust | Weekly. 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. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC off.
Which map has 1000x | Cross Rust | Weekly selected?
1000x | Cross Rust | Weekly runs a procedural map of size 3,000 with seed 1218474365, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does 1000x | Cross Rust | Weekly wipe, and on what schedule?
1000x | Cross Rust | Weekly wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 22 days 21 hours ago, and that is the one in play.
What is wipe day on 1000x | Cross Rust | Weekly like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 3.
Tags and filters
Which Rust Data filters and lists contain 1000x | Cross Rust | Weekly?
On Rust Data, 1000x | Cross Rust | Weekly appears in these lists: Modded Rust servers and Rust servers with more than 10x. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: More than 10x.
How should you read the server tags on 1000x | Cross Rust | Weekly?
These tags are published by 1000x | Cross Rust | Weekly and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join 1000x | Cross Rust | Weekly?
In Rust, F1 opens the console: type client.connect 135.148.15.102:23565. Launch Rust on this page does the same by opening the game through Steam and connecting.