Matt's Server
Offline 91.114.250.213:28015 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 159/250
- 188/250
- 587/675
- 35/100
- 681/775
- 554/625
Quick answers
from the figures on this pageWipe timing
What wipe timing does Matt's Server follow?
Its rhythm cannot be told from the wipes of Matt's Server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 55 days 13 hours ago.
Tags
How should you read the tags on Matt's Server?
These are the tags Matt's Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Matt's Server appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Matt's Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does Matt's Server hold among Rust servers?
Ranking for Matt's Server: #15,428 on seven-day player hours, top – of all ranked servers.
How full does Matt's Server get?
Matt's Server is not responding; status offline, last seen 41 days 12 hours ago.
Server
Where does Matt's Server sit?
Reading: location. Matt's Server 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 91.114.250.213:28015.
What Rust version is Matt's Server on?
Reading: Matt's Server, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
How reliable is Matt's Server, and is it online now?
Reading: offline. Matt's Server last answered 41 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 September 2026.
Map and rules
How is Matt's Server configured, and what rules are in force?
Check: gather rate. The name Matt's Server does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is Matt's Server on?
Check: map. Procedural, generated by the game, on Matt's Server.
Connection
How can you get onto Matt's Server?
To join: start Rust, press F1 and type client.connect 91.114.250.213:28015. Or press Launch Rust here and Steam opens the game and connects you.