Offline 207.136.64.12:28320 checked 34d ago
Phoenix Jungle Verification jungle-000
Connect
srv = rust.server("207.136.64.12:28322")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 08:25 UTC34d ago | 0 | NaN | 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 207.136.64.12:28320
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 08:25 UTC
- hostname
- –
- first seen
- 24 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 543 on average | 638/725 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 450/475 |
| 2 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 307 on average | 38/250 |
| 3 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 306 on average | 53/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 267 on average | 135/175 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 265 on average | 215/250 |
Quick answers
From the figures on this page.
Population
What position does Phoenix Jungle Verification jungle-000 take in the server rankings?
Rank #15,643 on seven-day player hours for Phoenix Jungle Verification jungle-000, within the top 71% of all ranked servers.
What population does Phoenix Jungle Verification jungle-000 carry?
Offline now for Phoenix Jungle Verification jungle-000, with the last sample 34 days 4 hours ago.
About the server
What is the Rust version on Phoenix Jungle Verification jungle-000?
Version Rust network protocol 2633 and build 165217 on Windows is reported by Phoenix Jungle Verification jungle-000. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Phoenix Jungle Verification jungle-000, and is it up?
Offline now for Phoenix Jungle Verification jungle-000, last seen 34 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 24 September 2026.
In which location is Phoenix Jungle Verification jungle-000 hosted?
There is no region published for Phoenix Jungle Verification jungle-000. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 207.136.64.12:28320.
Settings and map
Which rules apply on Phoenix Jungle Verification jungle-000, and what settings?
You will not find a gather rate in the string Phoenix Jungle Verification jungle-000. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.
Which map has Phoenix Jungle Verification jungle-000 loaded?
Phoenix Jungle Verification jungle-000 runs a procedural map, which the game generates.
Wipe data
When does Phoenix Jungle Verification jungle-000 wipe, and on what schedule?
Too few wipes are on record for Phoenix Jungle Verification jungle-000 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 34 days 5 hours ago.
On Phoenix Jungle Verification jungle-000, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold Phoenix Jungle Verification jungle-000, and which filters?
On Rust Data, Phoenix Jungle Verification jungle-000 appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on Phoenix Jungle Verification jungle-000 hold?
Read by the game's server browser, the tags Phoenix Jungle Verification jungle-000 publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join Phoenix Jungle Verification jungle-000?
Enter client.connect 207.136.64.12:28320 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.