Rust StatisticsWorking papers on every public Rust server · 44,156 players now

Phoenix Jungle Verification jungle-000

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 34d ago · 207.136.64.12:28320

Abstract

We describe the public Rust server Phoenix Jungle Verification jungle-000, reached at 207.136.64.12:28320. It is offline at the last check, against a seven-day mean of 01. It ranks #15,643 of all servers, the top 71%. It last wiped 35d 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.
MeasureValueNote
Players now0/10% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,643top 71%
Last wipe35d agono schedule published
Next wipe3–too few wipes 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 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 71% 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
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak0players, last three wipes
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 24 Sep, 08:2535d ago 0 – running 0

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 5: The map: Procedural Map.
Table 4: The server's published settings.
Address207.136.64.12:28320
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe24 Sep 2026, 08:25 UTC
Hostname–
First seen24 Sep 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 unmodded rust community servers [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 526 on average295/300
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average256/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average27/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 278 on average22/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average38/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 247 on average123/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Phoenix Jungle Verification jungle-000 based?

A region is not published by Phoenix Jungle Verification jungle-000. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 207.136.64.12:28320.

A.2How reliable is Phoenix Jungle Verification jungle-000, and is it currently online?

At the present moment, Phoenix Jungle Verification jungle-000 is offline; it was last seen 34 days 22 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 24 September 2026.

A.3What version of Rust is run on Phoenix Jungle Verification jungle-000?

The version of Rust on Phoenix Jungle Verification jungle-000 is network protocol 2633 and build 165217, and the operating system is Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does Phoenix Jungle Verification jungle-000 wipe?

Too few wipes by Phoenix Jungle Verification jungle-000 have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 35 days ago.

A.5What happens on Phoenix Jungle Verification jungle-000 when wipe day arrives?

Across its recent wipes, the average peak population was 0 players. The peak on the latest wipe came 0 hours after it began.

Population

A.6What position does Phoenix Jungle Verification jungle-000 occupy in the ranking of Rust servers?

Ranked by player hours across seven days, Phoenix Jungle Verification jungle-000 holds #15,643, in the top 71% of all ranked servers.

A.7How would you characterise the player activity on Phoenix Jungle Verification jungle-000?

Phoenix Jungle Verification jungle-000 is not online now; 34 days 22 hours have passed since it was last seen.

Tags, lists

A.8What is the meaning of the tags on Phoenix Jungle Verification jungle-000?

Tags from Phoenix Jungle Verification jungle-000, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): The slot count is 1; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): Joining requires the same game version: protocol 2633; cs165217 (Build): Build 165217 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can Phoenix Jungle Verification jungle-000 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Phoenix Jungle Verification jungle-000: Rust community servers, measured. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.10Under what rules and settings does Phoenix Jungle Verification jungle-000 operate?

Its name carries no gather rate for Phoenix Jungle Verification jungle-000. At 8 players, the group limit equals the game's default. The mode is survival, which means the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. Community is its category in the server browser. VAC is active: that is Valve's anti-cheat.

A.11On which map does Phoenix Jungle Verification jungle-000 take place?

A procedural map, generated by the game, is what Phoenix Jungle Verification jungle-000 runs.

How to join

A.12What steps are required to join Phoenix Jungle Verification jungle-000?

Press F1 inside Rust to open the console and enter client.connect 207.136.64.12:28320. 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 mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp1Max players. The slot count is 1.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. Joining requires the same game version: protocol 2633.
cs165217Build. Build 165217 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been 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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Unmodded rust community servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.