Rust Server TrendsSeismic network · station log
Recording Stations11,644 Players37,516 Active2,896 Wipes · 3 h63 48 h

Station XX-16010 · no signal

The Thursday Problem

Offline 157.85.90.161:28015 checked 24d ago

moddedoxide
Connect
Players now
0/ 75
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,010
top 71%
Last wipe
48d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16010 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 75 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 160 on average
39/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average
46/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
17/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
7/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
7/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on The Thursday Problem?

The Thursday Problem runs a procedural map of size 4,500 with seed 1163496358, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on The Thursday Problem?

The name of The Thursday Problem gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched off.

Population

How many players are recorded on The Thursday Problem right now?

No players are recorded on The Thursday Problem at this moment; it is offline, and the last sighting was 24 days 4 hours ago.

How does The Thursday Problem rank against other Rust servers?

On player hours for the past week, The Thursday Problem sits at #16,010, which puts it inside the top 71% of every ranked server.

Server facts

How reliably does The Thursday Problem stay online?

No contact with The Thursday Problem right now, and the last recorded contact was 24 days 4 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does The Thursday Problem run from?

No region is published by The Thursday Problem. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 157.85.90.161:28015 is the address it uses.

What build of Rust does The Thursday Problem use?

The Thursday Problem is running Rust network protocol 2633 and build 165217 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

How often does The Thursday Problem wipe, and on which days?

The rhythm of The Thursday Problem cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 48 days 1 hours is how long the current world has been running.

Lists and tags

What do the server tags on The Thursday Problem mean?

These are the tags The Thursday Problem publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp75 (Max players): 75 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does The Thursday Problem appear?

The Rust Server Trends lists that take in The Thursday Problem are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

How do you connect to The Thursday Problem?

You can connect by pressing F1 in Rust and typing client.connect 157.85.90.161:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://cdn.discordapp.com/icons/1516835928872587374/f7d24e4228c4bf8c28b854e01a42c2f4.webp?size=2048.

Instrument codes

Server tags

what each one means

Published as mp75,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp75
Max players 75 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build The game build is 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.