Telegram RegisterThe public register of Telegram
Telegram profile photo for poltergeist▼•ᴥ•▼

Channel

poltergeist▼•ᴥ•▼

@polkabark

2 usernames

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

465subscribers

+15 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002397394682
TypeChannel
Usernames@polkabark @PoLLbark
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/polkabark

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 76% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1468234.59 August 2026 — 450 subscribers9 August 2026 — 450 subscribers15 August 2026 — 455 subscribers24 August 2026 — 461 subscribers31 August 2026 — 1 subscribers17 September 2026 — 468 subscribers17 September 2026 — 468 subscribers18 September 2026 — 2 subscribers18 September 2026 — 465 subscribers4659 August 202618 September 2026
9 measurements spanning 41 days, net +15. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 21:40465+463
18 Sept 2026, 20:402-466
17 Sept 2026, 03:22468no change
17 Sept 2026, 02:47468+467
31 Aug 2026, 09:531-460
24 Aug 2026, 05:08461+6
15 Aug 2026, 19:25455+5
9 Aug 2026, 05:10450no change
9 Aug 2026, 01:15450first reading

Engagement

23 posts held, back to 9 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
89.3%
avg views ÷ 465 subscribers
Avg views / post
415
10 posts measured
Reaction rate
14.9%
reactions ÷ views · ER floor
Posts in window
10
of 23 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 15 September 2026
Posts held23 (9 July 202615 September 2026)
Views total4,152
Reactions total618
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Sept 2026, 03:22 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

1,944 reactions across 23 posts, in 17 distinct kinds. The most used accounts for 19.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 538187192774691189637419.2%
❤‍🔥35318.2%
31916.4%
custom 534370857922647838622911.8%
custom 53818527249481313341638.38%
🔥1206.17%
🍓1045.35%
🎉964.94%
🎃703.60%
💘381.95%
💋351.80%
🥰201.03%
🕊100.514%
🦄70.36%
💅40.206%
🍾10.051%
💯10.051%

Custom emoji. 3 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 are Telegram’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 23 of the 23 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 1,944 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 23 most recent posts we hold, published 9 July 2026 to 15 September 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
3
of 23 we hold a reading for · 13%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @polkabark. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 23 most recent posts we hold for this entry, published 9 July 2026 to 15 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

15 Sept 2026, 07:10 UTC157 views22 reactionsread 17 September 2026

Ребя вчера был прикол.....

custom 534370857922647838620🍓2

14 Sept 2026, 18:02 UTC213 views19 reactionsread 17 September 2026

Штоооо........

❤‍🔥14custom 53818527249481313343🍓1🕊1

14 Sept 2026, 18:02 UTC214 views54 reactionsread 17 September 2026
Photo

🔸🔸🔸🔸🔸🔸🔸🔸 информация указана на картинке :P Дедлайн — месяц❗ Обращаться ➡️ @pol_ksh

❤‍🔥36custom 53818527249481313349💋4🍓2🕊1custom 53437085792264783861custom 53818719277469118961

14 Sept 2026, 18:02 UTC210 views33 reactionsread 17 September 2026
Photo

Привет, это я — 🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸❗ Рада видеть вас в своем закутке, вот некоторая информация, которая может быть важна: Она/её • ENSP • 4w3 🌿🌿🌿🌿🌿🌿🌿🌿🌿🌿🌿🌿 🎃ССЫЛКИ: • щитпост • анонимка • тамблер • тви 〰️〰️〰️〰️〰️〰️〰️ 🎃ТЭГИ: ➡️связанные с моими осами и сеттингами #лор #осы #thesafehotel #hunters #deathsleisure ➡️ форматные #инфо #коммиш #трейд #скетчи #арт #видос 〰️〰️〰️〰️〰️〰️〰️ [‼️В канале может присутс

❤‍🔥18custom 53437085792264783866🕊4🍓2🎉1custom 53818527249481313341custom 53818719277469118961

6 Sept 2026, 15:34 UTC567 views79 reactionsread 17 September 2026
Photo

Милс любит дарквиппедов, а я люблю Милс❤ #скетчи #crk

custom 53437085792264783864116💋12🍓3🔥3🥰2💘1🕊1

5 Sept 2026, 13:04 UTC486 views35 reactionsread 17 September 2026
Forwarded from @paket111kPhoto

Всем доброго утречка и с началом осени ! Открываю предзаказы на брелочьки !! Длиться предзаказы будут 3 недели (до 22 сентября включительно). Связываться по поводу заказа со мной можете через личные сообщения тгк. Доставка совершается за ваш счет через Почту России/СДЭК, но в принципе при возможности могу и опробовать другие способы вх. О процессе изготовления брелочков и процессе рассылки буду информировать тут, чт

custom 5381871927746911896227🍓4🔥1🕊1

1 Sept 2026, 21:26 UTC595 views93 reactionsread 17 September 2026
Photo

Сумасшествие #brawlstars #скетчи #хьючаки

custom 534370857922647838657❤‍🔥15🍓127🕊1custom 53818719277469118961

31 Aug 2026, 12:08 UTC467 views39 reactionsread 17 September 2026
Forwarded from @SIROVAROVI_MILSSSPhoto

Pictures of you I'd been sleeping for hours, when you came to my house You'd been lost in a crowd, said you had to get out You were covered with tears and you said you were sad So you wanted to play Yes, you wanted to play 🍓🍓🍓 ДаркВиппеды любиме #арт #DarkWhipped #кукиран

custom 53437085792264783862311💘5

28 Aug 2026, 15:29 UTC621 views93 reactionsread 17 September 2026
Photo

Заказы сюда #скетчи #коммиш

custom 534370857922647838644custom 53818719277469118962215🥰4🍓2💋2💘2❤‍🔥1

24 Aug 2026, 19:11 UTC622 views151 reactions2 Starsread 17 September 2026
Photo

Что-то произошло #арт #fnafau #purplephone

❤‍🔥86🍓2520💘6custom 53818719277469118965custom 53437085792264783864💋2🎉1

8 Aug 2026, 12:42 UTC177 views45 reactionsread 9 August 2026
Forwarded from @vmsawyerPhoto

я обещал... я обещал фанартик.... по сути редрав но там он совсем древний те кто знают те знают @PoLLbark

custom 534370857922647838630custom 53818527249481313349💋4🍓1🔥1

Showing the 12 most recent of 23 posts we hold for @polkabark. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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 2 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.

Named by

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“poltergeist▼•ᴥ•▼” (@polkabark), 465 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/polkabark.

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.