Telegram RegisterThe public register of Telegram

Channel

⋆. 𐙚 ˚PolkaKPP

@PolkaKPP

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

719subscribers

+1 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-1002023701089
TypeChannel
Username@PolkaKPP
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/PolkaKPP

Growth

718719718.56 Aug 2026, 15:08 — 718 subscribers6 Aug 2026, 16:16 — 718 subscribers7 Aug 2026, 05:12 — 719 subscribers6 Aug 2026, 15:087 Aug 2026, 05:12
3 measurements taken within a single day, net +1. 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 718–719 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 05:12719+1
6 Aug 2026, 16:16718no change
6 Aug 2026, 15:08718first reading

Engagement

13 posts held, back to 29 July 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
43.5%
avg views ÷ 719 subscribers
Avg views / post
313
13 posts measured
Reaction rate
9.10%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 4 August 2026
Posts held13 (29 July 20264 August 2026)
Views total4,066
Reactions total370
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:16 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.

Reaction mix

370 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 45.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 546111142865826509316945.7%
12233.0%
custom 52535920865229048204411.9%
🍓174.59%
custom 521540598756071616861.62%
custom 523770005469268067261.62%
custom 526516077420823078861.62%

Custom emoji. 5 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 13 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 370reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 29 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 23:59 UTC223 views38 reactionsread 6 August 2026

Доброе утро... Сука 04:56 Сегодня я сваливаю от вас на 4 дня.. Не пишите не звоните 😔 У меня сплав, звёзды и палатки по расписанию В последнее время мало активничаю конечно.. У меня отпуск 👍 Но вот с 15 числа начнётся веселуха Два дня я спец гость Потом фотограф (Самое интересное что на всех мероприятиях я в новых КОСПЛЕЯХ)

27custom 52535920865229048208🍓3

Signed Адам ( ̄∇ ̄)

3 Aug 2026, 08:10 UTC298 views34 reactionsread 6 August 2026
Photo

Ближайшие коспланы ❤❤❤ Трио блондинов

custom 546111142865826509329🍓41

Signed Адам ( ̄∇ ̄)

3 Aug 2026, 04:33 UTC256 views18 reactionsread 6 August 2026
Forwarded from @polochkakppPhoto

Народ... Срочно вопрос Иду на индион Надо понять какой косплей делать Почитала я значит Поняла что алиенстейдж тоже по факту Инди проект Какой косплей брать? Если есть ещё идеи пишите пожалуйста

custom 5461111428658265093144

Signed Адам ( ̄∇ ̄)

3 Aug 2026, 01:00 UTC268 views22 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 5461111428658265093148

Signed Адам ( ̄∇ ̄)

2 Aug 2026, 20:04 UTC285 views33 reactionsread 6 August 2026
Video

👀

custom 546111142865826509320🍓7custom 52377000546926806726

Signed Адам ( ̄∇ ̄)

1 Aug 2026, 14:13 UTC317 views26 reactionsread 6 August 2026
Photo

В августе постараемся сделать дроп

21custom 52535920865229048205

Signed Адам ( ̄∇ ̄)

31 Jul 2026, 23:30 UTC311 views31 reactionsread 6 August 2026
Forwarded from @voltlolkeVideo

Video, posted without a caption

custom 525359208652290482022custom 521540598756071616863

Signed Адам ( ̄∇ ̄)

31 Jul 2026, 22:48 UTC328 views15 reactionsread 6 August 2026

Кстати Вкидываю инфу с 3 по 14 число я буду в Перми 😔 Так что пишите если будет желание увидеться

custom 546111142865826509315

Signed Адам ( ̄∇ ̄)

31 Jul 2026, 22:13 UTC338 views30 reactionsread 6 August 2026

Поздравляю! Мы проебали 2 месяца лета ❤❤❤

custom 546111142865826509322custom 526516077420823078861🍓1

Signed Адам ( ̄∇ ̄)

30 Jul 2026, 22:25 UTC398 views20 reactionsread 6 August 2026
Forwarded from @Kaveh_alPhoto

🤩🤩🤩🤩🤩🤩🤩🤩 🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🎀—𝐄𝐧 𝐚𝐭𝐭𝐞𝐧𝐝𝐚𝐧𝐭 𝐥𝐞 𝐣𝐮𝐠𝐞 𝐞𝐧 𝐜𝐡𝐞𝐟, 𝐢𝐥𝐬 𝐜𝐨𝐧𝐜𝐥𝐮𝐞𝐧𝐭 𝐮𝐧 𝐩𝐚𝐫𝐢: 𝐑𝐢𝐬𝐥𝐞𝐲 𝐩𝐚𝐫𝐢𝐞 𝐪𝐮𝐞 𝐍𝐞𝐯𝐢𝐥𝐥𝐞𝐭 𝐯𝐢𝐞𝐧𝐝𝐫𝐚 𝐬𝐞𝐮𝐥 𝐞𝐭 𝐂𝐥𝐨𝐫𝐢𝐧𝐝𝐚 𝐪𝐮'𝐚𝐯𝐞𝐜 𝐩𝐥𝐮𝐬𝐢𝐞𝐮𝐫𝐬 𝐠𝐚𝐫𝐝𝐢𝐞𝐧𝐬. 𝐋𝐞 𝐩𝐞𝐫𝐝𝐚𝐧𝐭 𝐝𝐨𝐢𝐭 𝐟𝐚𝐢𝐫𝐞 𝐮𝐧 𝐜𝐚𝐝𝐞𝐚𝐮 𝐚𝐮 𝐠𝐚𝐠𝐧𝐚𝐧𝐭. 🤩 ⚡⚡ ⛓️⛓️⛓️ 𝑹𝒕/𝒓𝒆𝒂𝒄𝒕𝒊𝒐𝒏𝒔 𝑷𝒉/𝒓𝒆𝒕𝒐𝒖𝒄𝒉 Wriothesley - https://t.me/vin_reyn Clorinde - https://t.me/Kaveh_al #Wriothesley #Clorinde #Genshin_impact.

custom 546111142865826509317🍓21

Signed Адам ( ̄∇ ̄)

30 Jul 2026, 21:28 UTC352 views39 reactionsread 6 August 2026
Photo

Интерактив) приняла от Куи Интерактив Показать животного, на которого вы похожи на фото с косплеем Передаю Тянь ❤

custom 5461111428658265093276custom 52535920865229048206

Signed Адам ( ̄∇ ̄)

30 Jul 2026, 17:16 UTC354 views36 reactionsread 6 August 2026
Video message

Video message, posted without a caption

27custom 54611114286582650938custom 52535920865229048201

Signed Адам ( ̄∇ ̄)

Showing the 12 most recent of 13 posts we hold for @PolkaKPP. 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 — 47,265 of 1,189,255entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 15 registered channels — 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.

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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“⋆. 𐙚 ˚PolkaKPP” (@PolkaKPP), 719 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/PolkaKPP.

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.