Fig. 1Players on [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni BaşlayanRG-S15432-01 · Sheet 1 of 12
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Fig. 2FPS, entities and memoryRG-S15432-02 · Sheet 2 of 12
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers, and #626 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S15432-03 · Sheet 3 of 12
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.9 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak3players, last three wipes
crowd held75%else halves by day 2
The first 48 hours of its last wipes
Sat 17 OctWed 14 OctSat 10 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
ScheduleExpected wipesRG-S15432-04 · Sheet 4 of 12
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 12:55 UTC11d ago
2
–
running
0
Wed 14 Oct, 14:55 UTC14d ago
2
held half
2.9 days
1
Sat 10 Oct, 12:55 UTC18d ago
5
halved by day 2
4.1 days
0
Wed 7 Oct, 14:56 UTC21d ago
6
held half
2.9 days
1
Sat 3 Oct, 12:55 UTC25d ago
8
held half
4.1 days
2
Thu 1 Oct, 17:55 UTCFW27d ago
4
–
1.8 days
0
Wed 30 Sep, 14:55 UTC28d ago
3
–
1.1 days
0
Sat 26 Sep, 12:55 UTC32d ago
6
held half
4.1 days
2
Wed 23 Sep, 14:55 UTC35d ago
3
held half
2.9 days
0
Sat 19 Sep, 12:55 UTC39d ago
7
halved by day 3
4.1 days
0
Wed 16 Sep, 14:56 UTC42d ago
4
held half
2.9 days
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.
Table 1Wipe logRG-S15432-05 · Sheet 5 of 12
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan online, and what uptime has been recorded?
[TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan is offline at this moment; 7 days 7 hours ago is when it was last seen. 15 of 168 hours up over the last 7 full days, which is 9% of the time. On 13 September 2026 is when Rust Graphs first saw it.
2.
What location is recorded for [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
A region is not published by [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 31.59.131.203:28015 is its address.
3.
On which Rust version is [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan running?
On Linux, [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan runs Rust network protocol 2634 and build 167781. To join, your game must be on the same protocol; Steam handles the update.
Counts
4.
What player count is recorded on [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
The latest refresh records [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan as offline, last seen 7 days 7 hours ago. Averaged across seven days, the player count is 0.
5.
Against other Rust servers, where is [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan placed?
Within the top 69% of all ranked servers: [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan at #15,432 for player hours, seven days recorded. #626 against other quad servers.
Schedules
6.
What is recorded on [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan on wipe day?
The recent wipes averaged a busiest count of 3 players. 1 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 75% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 2.
7.
Which times and days are wipes plotted at on [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
[TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan wipes at times that follow no pattern, so no next wipe can be predicted. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 11 days 9 hours ago.
Settings
8.
Which settings does [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan run, and what rules?
[TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan takes its gather rate from its name: 3x. Groups: 4 players maximum (quad). survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.
9.
What is the map for [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
Seed 55555 and size 3,500 define the procedural map [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: FPS+ | Tem Map.
Tags
10.
On Rust Graphs, which lists and filters contain [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
The Rust Graphs lists that carry [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan are: 3x Rust servers, plotted and Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Last wipe: In the last 2 weeks; Gather rate: 3x.
11.
Which meaning is attached to each tag on [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
Tags published by [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp200 (Max players): 200 player slots; ts4 (Group limit): The team limit is 4; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): 167781 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
12.
Who is the operator of [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
The temrust.com.tr hostname [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan publishes is not used by any other server we track.
Connect
13.
What is the way to connect to [TR] TEM 3X Solo/Duo/Trio/Quad | Yeni Başlayan?
Connect with client.connect 31.59.131.203:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://zulabank.com is its website.
NotesAnswered from the figuresRG-S15432-11 · Sheet 11 of 12
Key
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,gmrust,cs167781,ts4,^o^z
Game
gmrust
Game modeSurvival in standard Rust style.
mp200
Max players200 player slots.
ts4
Group limitThe team limit is 4.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs167781
Build167781 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
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.
KeyTag string decodedRG-S15432-12 · Sheet 12 of 12