Offline 45.140.129.126:10300 checked 27d ago
Rust Server by JPT3F
Connect
srv = rust.server("45.140.129.126:10301")
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, measured since 2 Oct. 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 best
Top 60% 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 3, 3 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 06:59 UTC27d ago | 3 | 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
3000 · seed 6738
- map
- Procedural Map
- size
- 3000
- seed
- 6738
Server
srv.info()- address
- 45.140.129.126:10300
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 08:46 UTC
- hostname
- –
- first seen
- 2 Oct 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 · 151 on average | 87/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 60/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 170/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Rust Server by JPT3F rank?
Player hours over seven days put Rust Server by JPT3F at #13,806, in the top 60% of the ranked set.
How many players does Rust Server by JPT3F hold at once?
Rust Server by JPT3F returns no live count at this refresh, having last been seen 27 days 9 hours ago.
About the server
What is the Rust version on Rust Server by JPT3F?
Version Rust network protocol 2634 and build 166494 on Windows is reported by Rust Server by JPT3F. The protocol has to match before you can join, and Steam does the updating.
How reliable is Rust Server by JPT3F, and is it up?
Offline now for Rust Server by JPT3F, last seen 27 days 9 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 2 October 2026.
Where does Rust Server by JPT3F sit?
For Rust Server by JPT3F, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 45.140.129.126:10300 is its address.
Map and rules
Which settings and rules does Rust Server by JPT3F run?
No gather rate appears in the name: Rust Server by JPT3F. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Rust Server by JPT3F selected?
Rust Server by JPT3F runs a procedural map of size 3,000 with seed 6738, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Rust Server by JPT3F wipe, and on what schedule?
Too few wipes are on record for Rust Server by JPT3F to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days 11 hours ago.
What is wipe day on Rust Server by JPT3F like?
Across recent wipes the busiest point averaged 3 players. 3 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold Rust Server by JPT3F, and which filters?
The Rust Data lists that Rust Server by JPT3F fits are: Modded Rust servers. These filters bring it up 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 Rust Server by JPT3F?
The game's server browser reads these tags from Rust Server by JPT3F: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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.
How to join
What is the way into Rust Server by JPT3F?
The manual route: launch Rust, F1, then client.connect 45.140.129.126:10300. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.
