Statistical profileOnline
Matthew's Rust Server
157.85.86.77:20544 checked 6m ago
Connect to this server
1. Main points
Players now
1/ 40
2% full
7-day average
2
peak 3
Rank
#6,984
top 31%
Last wipe
8h ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 1 players on it, 2% of its 40 slots.
- Over the last seven days it averaged 2 players, with a peak of 3.
- It ranks #6,984 of all ranked servers, the top 31%, on player hours over the last seven days.
- Its current map went up 8h ago.
2. Players
Figure 1: Players on Matthew's Rust Server
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 31% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 19:33 UTC8h ago | – | – | running | 1 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
8. Server characteristics
Table 3: Characteristics of Matthew's Rust Server
What the server publishes and what was recorded
| Address | 157.85.86.77:20544 |
|---|---|
| Region | – |
| Max players | 40 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 27 Oct 2026, 19:33 UTC |
| Hostname | – |
| First seen | 27 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 159 on average | 44 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 47 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 21 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 7 / 1000 |
10. Quick answers
From the figures on this page.
Wipe details
When does Matthew's Rust Server wipe, and how often?
With too few wipes of Matthew's Rust Server on record, its rhythm remains unclear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 8 hours ago.
Server details
What does the record show for the uptime and current status of Matthew's Rust Server?
This release records Matthew's Rust Server as online. The uptime it reports puts the last restart at about 6 hours ago. The first sighting of it by Rust Census was on 27 October 2026.
Does Matthew's Rust Server hold a steady frame rate and connection?
The figures for the last 48 hours give an average of 168 server fps and a minimum of 150. Buildings, deployables and everything else in the world took the entity count to 48,568. The peak memory use recorded was 2,953 MB. What players experience as lag is low fps combined with a climbing entity count.
Which location does Matthew's Rust Server run from?
A region is not published by Matthew's Rust Server. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. 157.85.86.77:20544 is its address.
Which Rust version is Matthew's Rust Server running?
This release lists Matthew's Rust Server on Rust network protocol 2635 and build 168909, running on Linux. The same protocol is required for your game to join, and Steam updates it for you.
Population
What are the current player figures for Matthew's Rust Server?
Matthew's Rust Server stands at 1 players from 40 slots in this release. This release records a seven-day average of 2 players and a peak of 3. Over the past 48 hours the highest average fell at 00:00 UTC: 3 players.
How does Matthew's Rust Server compare with other servers in the rankings?
The rank for Matthew's Rust Server is #6,984 on seven-day player hours, in the top 31% of ranked servers.
Tag details
On Rust Census, which lists and filters carry Matthew's Rust Server?
Included in these Rust Census lists is Matthew's Rust Server: Modded Rust servers, counted. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
What is meant by each tag shown on Matthew's Rust Server?
Read by the game's server browser, Matthew's Rust Server publishes these tags: gmrust (Game mode): Survival play, in the standard Rust format; mp40 (Max players): Slots: 40; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): The server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Rules, map
What map is listed for Matthew's Rust Server?
Size 3,000 and seed 69420: that is the procedural map on Matthew's Rust Server, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
How is Matthew's Rust Server configured, and what rules does it keep?
No gather rate is recorded for Matthew's Rust Server in its name. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Plugins or settings change the game, and the browser lists it under Modded. Plugins on it number Oxide. Anti-cheat is active: VAC, Valve's system, is on.
How to join
How can you connect to Matthew's Rust Server?
Enter client.connect 157.85.86.77:20544 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp40 | Max players Slots: 40. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.