Telegram RegisterThe public register of Telegram
Telegram profile photo for Arrakken PVP

Channel

Arrakken PVP

@arrakken_pvp

On this record: Growth · Engagement · Posts · Citations · Cite this entry

42subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002418923569
TypeChannel
Username@arrakken_pvp
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/arrakken_pvp

Growth

426 August 2026 — 42 subscribers10 August 2026 — 42 subscribers6 August 202610 August 2026
2 measurements spanning 5 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 41–43 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:0142no change
6 Aug 2026, 00:5542first reading

Engagement

20 posts held, back to 9 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.8%
avg views ÷ 42 subscribers
Avg views / post
4.5
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held20 (9 August 202610 August 2026)
Views total91
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 17:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

10 Aug 2026, 10:30 UTC4 viewsread 10 August 2026

🏹 📒 NFT #754 H3 F27 [Сад теней] Рыжуля не смогла победить на охоте сложности 1.41 на земле #1285 Получено повреждений: 6 Остатки хитов: 100% ⚙️ Получено 20036 опыта Владелец планеты получил 0 золота за форт

10 Aug 2026, 10:29 UTC4 viewsread 10 August 2026

🏹 📗 NFT #4200 H7 MC237 [TOP14] [Сад теней] Оружейник победила на охоте сложности 1.19 на земле #1285 Получено повреждений: 17 Остатки хитов: 100% ⚙️ Получено 190420 опыта 📦 Получено 120 руда 🛖 Получено 171 очков охоты Владелец планеты получил 0 золота за форт

10 Aug 2026, 10:28 UTC4 viewsread 10 August 2026

🏹 📒 NFT #3655 H6 MC80 [Сад теней] ТарантаС не смогла победить на охоте сложности 1.77 на земле #1285 Получено повреждений: 2 Остатки хитов: 100% ⚙️ Получено 7857 опыта Владелец планеты получил 0 золота за форт

10 Aug 2026, 10:28 UTC4 viewsread 10 August 2026

♻️ NFT #106 H4 M39 [Сад теней] Смотритель восстановила хиты до 100% Владелец планеты получил 406 золота от таможни

10 Aug 2026, 10:28 UTC3 viewsread 10 August 2026

🏹 📕 NFT #106 H4 M39 [Сад теней] Смотритель проиграла на охоте сложности 2.47 на земле #1011 Получено повреждений: 8 Остатки хитов: 0% ⚙️ Получено 6282 опыта Владелец планеты получил 1231 золота за форт

10 Aug 2026, 05:18 UTC4 viewsread 10 August 2026

🏹 📗 NFT #4310 H1 MC101 [TOP20] [Бинго] КотоПес победила на охоте сложности 1.2 на земле #1386 Получено повреждений: 116 Остатки хитов: 33% ⚙️ Получено 158990 опыта 📦 Получено 220 витон 🛖 Получено 108 очков охоты Владелец планеты получил 515 золота за форт

10 Aug 2026, 05:18 UTC4 viewsread 10 August 2026

🏹 📒 NFT #4136 A7 MC110 [TOP4] [Бинго] Бульдог не смогла победить на охоте сложности 1.38 на земле #1322 Получено повреждений: 54 Остатки хитов: 100% ⚙️ Получено 19459 опыта Владелец планеты получил 515 золота за форт

10 Aug 2026, 05:18 UTC4 viewsread 10 August 2026

🏹 📗 NFT #3750 H6 AN124 [TOP13] [Бинго] Меховой победила на охоте сложности 1.05 на земле #1365 Получено повреждений: 2 Остатки хитов: 100% ⚙️ Получено 703685 опыта 📦 Получено 80 руда 🛖 Получено 111 очков охоты Владелец планеты получил 515 золота за форт

10 Aug 2026, 05:18 UTC4 viewsread 10 August 2026

♻️ NFT #3088 A7 F87 [TOP22] [Бинго] VALKIRIY восстановила хиты до 100% Владелец планеты получил 467 золота от таможни

10 Aug 2026, 05:18 UTC4 viewsread 10 August 2026

🏹 📕 NFT #3088 A7 F87 [TOP22] [Бинго] VALKIRIY проиграла на охоте сложности 1.33 на земле #1366 Получено повреждений: 27 Остатки хитов: 0% ⚙️ Получено 5475 опыта Владелец планеты получил 515 золота за форт

10 Aug 2026, 05:17 UTC4 viewsread 10 August 2026

♻️ NFT #2870 A6 MC109 [TOP9] [Бинго] Ящерица восстановила хиты до 100% Владелец планеты получил 494 золота от таможни

10 Aug 2026, 05:17 UTC4 viewsread 10 August 2026

🏹 📕 NFT #2870 A6 MC109 [TOP9] [Бинго] Ящерица проиграла на охоте сложности 1.78 на земле #1260 Получено повреждений: 95 Остатки хитов: 0% ⚙️ Получено 9453 опыта Владелец планеты получил 515 золота за форт

Showing the 12 most recent of 20 posts we hold for @arrakken_pvp. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 909,027 of 1,481,346entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Arrakken PVP” (@arrakken_pvp), 42 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/arrakken_pvp.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.