Imgfire PoC

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 20d ago · 84.173.133.95:28015

Abstract

We describe the public Rust server Imgfire PoC, reached at 84.173.133.95:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,854 of all servers, the top 72%. It last wiped 25d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/10	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,854	top 72%
Last wipe	25d ago	no schedule published
Next wipe³	–	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.

No hourly history yet.

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 memory⁴. 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 72% 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.

RankRank in region

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)	Peak	Crowd	Lasted	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. 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.

Address	`84.173.133.95:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	3 Oct 2026, 19:19 UTC
Hostname	–
First seen	5 Oct 2026
Map	Procedural 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 rust community servers listed [2] and upcoming Rust wipes [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rusty Moose \|EU Mondays\|EU · groups of 12+ · weekly · 565 on average	220/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average	129/200
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 291 on average	28/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average	14/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average	23/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average	32/225

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does Imgfire PoC have?

A region is not published by Imgfire PoC. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 84.173.133.95:28015.

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

Imgfire PoC is currently offline, with the last sighting 20 days 1 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. The first record of it by Rust Statistics dates to 5 October 2026.

A.3What version of Rust is run on Imgfire PoC?

Imgfire PoC is running Rust network protocol 2634 and build 166652 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does Imgfire PoC follow for wipes?

The record of Imgfire PoC's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 25 days 5 hours have passed since the current world was generated.

Player count

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

The seven-day player-hours ranking puts Imgfire PoC at #15,854, within the top 72% of ranked servers.

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

The last recorded sighting of Imgfire PoC was 20 days 1 hours ago; it is offline now.

Tags, lists

A.7How should the tags on Imgfire PoC be interpreted?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166652 (Build): Build 166652 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set, which Imgfire PoC publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

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

These Rust Statistics lists include Imgfire PoC: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

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

No gather rate appears in the name of Imgfire PoC. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. It is a community server, as the browser's Community listing shows. VAC is inactive: the anti-cheat from Valve is off.

A.10On which map does Imgfire PoC take place?

The game generates the map on Imgfire PoC; that format is procedural.

Connection

A.11What steps are required to join Imgfire PoC?

Press F1 inside Rust to open the console and enter client.connect 84.173.133.95:28015. 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 mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp10`	Max players. 10 slots are available.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2634`	Protocol. The game protocol is 2634; your client must match it to join.
`cs166652`	Build. Build 166652 is the one running.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. No region code is set.

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. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.