Offline 157.85.90.161:28015 checked 24d ago
The Thursday Problem
Connect
srv = rust.server("157.85.90.161: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, measured since 17 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 71% 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
4500 · seed 1163496358
- map
- Procedural Map
- size
- 4500
- seed
- 1163496358
Server
srv.info()- address
- 157.85.90.161:28015
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Sep 2026, 01:49 UTC
- hostname
- –
- first seen
- 13 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 | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 89 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population data
What position does The Thursday Problem take in the server rankings?
Over the last seven days The Thursday Problem sits at #16,010 on player hours, in the top 71% of ranked servers.
How many players does The Thursday Problem hold at once?
The Thursday Problem returns no live count at this refresh, having last been seen 24 days 18 hours ago.
Server data
Which Rust version is The Thursday Problem on?
Rust network protocol 2633 and build 165217 on Linux is what The Thursday Problem runs. Steam updates your game for you, but the protocol must match to join.
How reliable is The Thursday Problem, and is it online now?
The Thursday Problem is offline at this refresh; the last response came 24 days 18 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does The Thursday Problem run from?
For The Thursday Problem, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 157.85.90.161:28015.
Map and rules
Which rules apply on The Thursday Problem, and what settings?
No gather rate appears in the name: The Thursday Problem. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
Which map has The Thursday Problem selected?
The game generates the map on The Thursday Problem: procedural, size 4,500, seed 1163496358. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does The Thursday Problem wipe, and how often?
A rhythm cannot be read from the wipes of The Thursday Problem on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 48 days 15 hours ago.
Lists and tags
Which lists on Rust Data hold The Thursday Problem, and which filters?
The Rust Data lists that The Thursday Problem fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on The Thursday Problem hold?
The game's server browser reads these tags from The Thursday Problem: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into The Thursday Problem?
The manual route: launch Rust, F1, then client.connect 157.85.90.161:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://cdn.discordapp.com/icons/1516835928872587374/f7d24e4228c4bf8c28b854e01a42c2f4.webp?size=2048.