🌟 🤩покойной ночи всем, кроме тех... 🌟🌟🌟кто ни разу не праздновал/отмечал Хэллоуин!!🌟 🌟 — я получаю!!! 🌟 — я не получаю💔 услышано хоукинс || подписывайся
custom 5399849041645316636101custom 540017102245859687749

Channel
@HelpFrPerl_00
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
5,750subscribers
-970 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002209874434 |
|---|---|
| Type | Channel |
| Username | @HelpFrPerl_00 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/HelpFrPerl_00 |
Gaming — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 06:19 | 5,750 | -6 |
| 4 Nov 2026, 09:10 | 5,756 | -16 |
| 1 Nov 2026, 12:21 | 5,772 | -18 |
| 29 Oct 2026, 15:56 | 5,790 | -12 |
| 26 Oct 2026, 20:18 | 5,802 | -28 |
| 23 Oct 2026, 23:06 | 5,830 | -30 |
| 21 Oct 2026, 03:15 | 5,860 | -48 |
| 17 Oct 2026, 22:34 | 5,908 | -23 |
| 14 Oct 2026, 20:17 | 5,931 | -35 |
| 11 Oct 2026, 06:01 | 5,966 | -38 |
| 4 Oct 2026, 17:41 | 6,004 | -105 |
| 24 Sept 2026, 20:55 | 6,109 | -110 |
| 16 Sept 2026, 16:20 | 6,219 | -65 |
| 13 Sept 2026, 03:55 | 6,284 | -56 |
| 9 Sept 2026, 08:59 | 6,340 | -81 |
| 4 Sept 2026, 07:00 | 6,421 | -36 |
| 31 Aug 2026, 14:13 | 6,457 | -27 |
| 28 Aug 2026, 07:44 | 6,484 | -35 |
| 25 Aug 2026, 00:03 | 6,519 | -43 |
| 21 Aug 2026, 02:05 | 6,562 | first reading |
37 posts held, back to 11 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 26 October 2026 |
|---|---|
| Posts held | 37 (11 July 2026 – 26 October 2026) |
| Views total | 12,595 |
| Reactions total | 994 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 4 Nov 2026, 19:07 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.
4,291 reactions across 36 posts, in 57 distinct kinds. The most used accounts for 6.71% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5474283273016346893 | 288 | 6.71% | |
| custom 5442926665976031687 | 200 | 4.66% | |
| custom 5370605953651610465 | 191 | 4.45% | |
| custom 5422570342059114321 | 188 | 4.38% | |
| custom 5303144545851054470 | 185 | 4.31% | |
| custom 5305651758779902901 | 177 | 4.12% | |
| custom 5386597418269711935 | 171 | 3.99% | |
| custom 5305389057105242534 | 163 | 3.80% | |
| custom 5399859036034211606 | 156 | 3.64% | |
| custom 5197295441913359714 | 145 | 3.38% | |
| custom 5465268974180672299 | 144 | 3.36% | |
| custom 5404614170421276474 | 141 | 3.29% | |
| custom 5422859951703885471 | 131 | 3.05% | |
| custom 5363829942662499388 | 121 | 2.82% | |
| custom 5399849041645316636 | 106 | 2.47% | |
| custom 5305599471848037064 | 102 | 2.38% | |
| custom 5399905292831991992 | 92 | 2.14% | |
| custom 5400299373261269103 | 66 | 1.54% | |
| custom 5431580375992273224 | 65 | 1.51% | |
| custom 5440677662186052053 | 57 | 1.33% | |
| 37 further kinds | 1,402 | 32.7% |
Custom emoji. Every row above is a 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 36 of the 37 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 4,291 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 11 July 2026 to 26 October 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @HelpFrPerl_00. 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 37 most recent posts we hold for this entry, published 11 July 2026 to 26 October 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.
Telegram’s own ‘edited’ marker: 4 of 19 posts held from the last 30 days (21.1%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🌟 🤩покойной ночи всем, кроме тех... 🌟🌟🌟кто ни разу не праздновал/отмечал Хэллоуин!!🌟 🌟 — я получаю!!! 🌟 — я не получаю💔 услышано хоукинс || подписывайся
custom 5399849041645316636101custom 540017102245859687749
Sticker, posted without a caption
custom 53998490416453166364custom 54001710224585968774
🤩oroscopes from 🤩erl 🌟 🌟 на неделю! (26.10 — 01.11) 🌟Овен — любите пауков? а вот они вас очень... 🌟🌟Телец — надеюсь, что вы не боитесь темноты...🌟 🍁Близнецы — вас ждет счастливый Хэллоуин, который вы проведёте с друзьями/родными! 🌟🌟Рак — упс, кажется вас ждет много неудач... 🌟Лев — забудьте про все страхи на этой неделе: все будет хорошо! 🌟🌟Дева — пора пересмотреть всевозможные Хэллоуинские фильмы!!!! 🌟Весы — к…
custom 540015150183223223244custom 539995384743727527425
Sticker, posted without a caption
custom 53999538474372752743custom 53998490416453166361
Давайте много реакций!! 🌟 Напоминаю, что с завтрашнего дня начинается тематическая неделя Хэллоуина!! Вас ждет много всего💋🌟
custom 539990529283199199233custom 540029937326126910326
🤩rᥱmіᥙm 🌟🌟 ᥱm᥆ȷі 🎀subscribe — @HelpFrPerl_00 🤩ремиум эмодзи с вайбом Хэллоуина(пнг) 🎀🎀🎀 🌟 click 🌟 🎀🎀🎀 #Эмодзи #Рандом || boost
custom 539990529283199199259custom 540029937326126910340
🤩так, правильный ответ — номер 3!! Это обо мне — не правда🍒 🌟🌟🍉 Я шарю за осд с 2024 года!!🍉
custom 531243393734204531729custom 531210358993247387516
Sticker, posted without a caption
🌟🌟🌟 🤩 правды, 🤩 ложь Попробуйте угадать, что из этого обо мне — не правда!! 1. Мой нелюбимый цвет из радуги — красный🍉 2. Мои самые любимые цветы это лилии🍉 3. Я шарю за осд с 2022 года🍉 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🌟🌟 Правильный ответ выложу через 5-10 минут ! ! 🌟 услышано хоукинс || подписывайся
custom 531475725695114506129custom 531478133883277327319
Sticker, posted without a caption
custom 53121035899324738754
Posted without readable text
custom 537060595365161046537custom 536832653719821694924
Sticker, posted without a caption
custom 537060595365161046516custom 536832653719821694911
Showing the 12 most recent of 37 posts we hold for @HelpFrPerl_00. 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.
We recorded 1 post on @HelpFrPerl_00 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“🎃 Услышано Хоукинс | интерактивы и стикеры по всем фд || эмодзи по всем фд” (@HelpFrPerl_00), 5,750 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/HelpFrPerl_00.
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.