Rust StatisticsWorking papers on every public Rust server · 93,889 players now

RektingTlsLocalTest

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 17h ago · 85.245.30.92:38145

Abstract

We describe the public Rust server RektingTlsLocalTest, reached at 85.245.30.92:38145. It is offline at the last check, against a seven-day mean of 01. It ranks #15,434 of all servers, the top 70%. It last wiped 7d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/80% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,434top 70%
Last wipe7d agono schedule published
Next wipe3–no wipe seen yet

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.

AveragePeak
0123421:0022:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

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).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 70% 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.

No rank history yet.
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

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

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. 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

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address85.245.30.92:38145
Region–
Max players8
Group limit8, the default
Wipe schedule–
Last wipe14 Nov 2026, 13:38 UTC
Hostname–
First seen20 Nov 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and predicted wipe schedule [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
МИНИ-КАРТА 2Х | STORM | FPS+ 21.11EU · groups of 8+ · weekly · 128 on average132/100
ShockRust | Blue | NoLimitno group limit · 110 on average288/400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11EU · groups of 16+ · weekly · 98 on average190/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11EU · groups of 16+ · monthly · 79 on average78/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11EU · groups of 16+ · monthly · 68 on average128/1000
ShockRust | Green | MAX 4no group limit · 65 on average135/250

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does RektingTlsLocalTest have?

No region is published by RektingTlsLocalTest. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 85.245.30.92:38145.

A.2What is the reliability of RektingTlsLocalTest, and is it online?

At the present moment, RektingTlsLocalTest is offline; it was last seen 17 hours ago. It was first observed on 20 November 2026 by Rust Statistics.

A.3What version of Rust is run on RektingTlsLocalTest?

Rust network protocol 2636 and build 170545 is the version that RektingTlsLocalTest runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4On what cycle does RektingTlsLocalTest wipe?

Too few wipes by RektingTlsLocalTest have been recorded to determine the pattern. Thursday 3 December at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 7 days 1 hours have passed since the current world was generated.

Player count

A.5What is the rank of RektingTlsLocalTest among Rust servers?

The seven-day player-hours ranking puts RektingTlsLocalTest at #15,434, within the top 70% of ranked servers.

A.6At what level does RektingTlsLocalTest operate in terms of players?

RektingTlsLocalTest is not online now; 17 hours have passed since it was last seen. Averaged across the last seven days, the population is 0 players.

Tags, lists

A.7How should the tags on RektingTlsLocalTest be interpreted?

gmrust (Game mode): Survival on standard Rust rules; mp8 (Max players): The slot count is 8; ts8 (Group limit): 8 per team, the value the game sets by default; v2636 (Protocol): Your game must run protocol 2636 to connect; cs170545 (Build): Build 170545 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags RektingTlsLocalTest publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can RektingTlsLocalTest be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that RektingTlsLocalTest fits. 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 2 weeks.

Rules, settings, map

A.9What are the settings and rules that govern RektingTlsLocalTest?

The name of RektingTlsLocalTest states no gather rate. 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.10On which map does RektingTlsLocalTest take place?

A procedural map, generated by the game, is what RektingTlsLocalTest runs.

Connection

A.11What is the process for joining RektingTlsLocalTest?

Press F1 inside Rust to open the console and enter client.connect 85.245.30.92:38145. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp8,ptrak,$r?,v2636,gmrust,cs170545,ts8,^o^z.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp8Max players. The slot count is 8.
ts8Group limit. 8 per team, the value the game sets by default.
v2636Protocol. Your game must run protocol 2636 to connect.
cs170545Build. Build 170545 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. 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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.