Offline 81.64.227.182:28015 checked 31d ago
Development J2P
Connect
srv = rust.server("81.64.227.182:28017")
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 | Sun 27 Sep, 16:54 UTC31d 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
- 81.64.227.182:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 16:54 UTC
- hostname
- –
- first seen
- 27 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 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 36/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 56/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population
What position does Development J2P take in the server rankings?
Player hours over seven days put Development J2P at #16,968, in the top 71% of the ranked set.
How full does Development J2P run?
Development J2P returns no live count at this refresh, having last been seen 31 days 11 hours ago.
Server data
What Rust version does Development J2P run?
The build is Rust network protocol 2633 and build 165217 on Windows, run by Development J2P. Joining needs the same protocol on your game; Steam handles the update.
Is Development J2P up, and what does its uptime show?
The latest sample has Development J2P offline, with a last sighting 31 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 27 September 2026.
Which location does Development J2P run from?
There is no region published for Development J2P. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 81.64.227.182:28015 is its address.
Rules, settings, map
Which settings and rules does Development J2P run?
No gather rate appears in the name: Development J2P. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Development J2P?
Development J2P runs a procedural map, which the game generates.
Wipe schedule
When does Development J2P wipe, and on what schedule?
The record for Development J2P holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 31 days 11 hours ago.
On Development J2P, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold Development J2P, and which filters?
The Rust Data lists that Development J2P fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Development J2P?
The game's server browser reads these tags from Development J2P: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Development J2P?
Enter client.connect 81.64.227.182:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.