Thomasserver
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 9m ago · 51.79.46.151:25053
Abstract
We describe the public Rust server Thomasserver, reached at 51.79.46.151:25053. At the last check it held 0 of 75 places, against a seven-day mean of 1 and a peak of 31. It ranks #3,791 of all servers, the top 17%. It last wiped 6d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 17% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 3 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 22 Oct, 21:306d ago | 3 | – | running | 1 |
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 51.79.46.151:25053 |
|---|---|
| Region | – |
| Max players | 75 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 22 Oct 2026, 21:30 UTC |
| Hostname | – |
| First seen | 22 Oct 2026 |
| Map | Procedural Map |
| Size | 3000 |
| Seed | 1 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and next Rust wipe times [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 149 on average | 173/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average | 81/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average | 20/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average | 24/1000 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average | 260/700 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1How well does Thomasserver run?
Over the past 48 hours, it ran at an average of 180 server fps, with a low of 111. Buildings, deployables and all other world objects counted together reached a maximum of 49,689 entities. Its highest memory usage was 3,789 MB. When fps is low and entity count climbs, players feel lag.
A.2What is the location of Thomasserver?
There is no region published for Thomasserver. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 51.79.46.151:25053 is its address.
A.3What is the online status and reliability of Thomasserver?
Thomasserver is online at this time. The uptime it reports indicates a restart about 2 days 20 hours ago. The server was up 99% of the time over the last 6 full days, 143 of 144 hours. The first record of it by Rust Statistics dates to 22 October 2026.
A.4What version of Rust is run on Thomasserver?
Rust network protocol 2635 and build 168909 is the version that Thomasserver runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.5What schedule does Thomasserver follow for wipes?
The record of Thomasserver's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 6 days 15 hours have passed since the current world was generated.
A.6What characterises wipe day on Thomasserver?
Across its recent wipes, the average peak population was 3 players. The peak on the latest wipe came 22 hours after it began.
Population
A.7How does Thomasserver compare with other Rust servers in the rankings?
The seven-day player-hours ranking puts Thomasserver at #3,791, within the top 17% of ranked servers.
A.8At what level does Thomasserver operate in terms of players?
On Thomasserver, 0 of the 75 slots are occupied at present. The peak over seven days is 3, against an average of 1. Of the last 48 hours, the peak hour falls at 23:00 UTC, with an average of 2 players.
Tags and filters
A.9What do the tags associated with Thomasserver signify?
Tags from Thomasserver, read by the game's server browser, are gmrust (Game mode): Rust survival, in its standard form; mp75 (Max players): The slot count is 75; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.10Where can Thomasserver be found among the Rust Statistics lists and filters?
The Rust Statistics lists that Thomasserver fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Rules, settings, map
A.11Under what rules and settings does Thomasserver operate?
Its name carries no gather rate for Thomasserver. The group cap is 8 players, which is the default in the game. survival is the game mode here; gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.
A.12What map is in use on Thomasserver?
Generated by the game from seed 1, the procedural map on Thomasserver measures 3,000. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
Connection
A.13How do you connect to Thomasserver?
Enter client.connect 51.79.46.151:25053 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.
Appendix BServer tags
What each of the server's tags means. Published as mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp75 | Max players. The slot count is 75. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2635 | Protocol. Your game must run protocol 2635 to connect. |
cs168909 | Build. This server runs game build 168909. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. The region code is unset. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. The game is altered by plugins or settings, so it is listed as 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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.