RUST METRICSFlight deck · live data
Data live Servers11,722 Players54,556 Populated3,373 Fresh wipes 3 h135 Scan5 min
‹ All servers157.85.90.161:28015
Offline Full Queue Fresh wipe Wipe due No query

The Thursday Problem

Offline 157.85.90.161:28015 checked 24d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 19 38 56 75 PAX 0 /75

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#16,010top 71%
Last wipe47d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What wipe timing does The Thursday Problem follow?

Its rhythm cannot be told from the wipes of The Thursday Problem on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 47 days 22 hours ago.

Tag meanings

How should you read the tags on The Thursday Problem?

These are the tags The Thursday Problem publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp75 (Max players): 75 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show The Thursday Problem?

These Rust Metrics lists carry The Thursday Problem: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does The Thursday Problem hold among Rust servers?

Ranking for The Thursday Problem: #16,010 on seven-day player hours, top 71% of all ranked servers.

How full does The Thursday Problem get?

Reading for The Thursday Problem: offline at this moment; last seen 24 days 1 hours ago.

Server details

Which location does The Thursday Problem run from?

Reading: location. The Thursday Problem gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 157.85.90.161:28015.

What Rust version is The Thursday Problem on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by The Thursday Problem. Matching protocol is required to join. Let Steam update your game.

How reliable is The Thursday Problem, and is it online now?

The Thursday Problem reports offline. The last reading came 24 days 1 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What rules does The Thursday Problem enforce, and what are its settings?

Reading the name gives no gather rate for The Thursday Problem. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is off. That is Valve's anti-cheat.

Which map is live on The Thursday Problem?

From seed 1163496358, the game generates the procedural map on The Thursday Problem. Its size is 4,500. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to The Thursday Problem?

To join: start Rust, press F1 and type client.connect 157.85.90.161:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://cdn.discordapp.com/icons/1516835928872587374/f7d24e4228c4bf8c28b854e01a42c2f4.webp?size=2048.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp75
Max players 75 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.