Жду потом ваши комментарии после прослушивания о том как вам такой формат работ. На первый раз постарался сделать лайтовый хоррор. 😜
custom 5330558832475147629190custom 533042776295817973851custom 533025712820248010419custom 52152000653536946823

Channel
@hollyavele
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
14,869subscribers
+354 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002291607480 |
|---|---|
| Type | Channel |
| Username | @hollyavele |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/hollyavele |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 17 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 17:00 | 14,869 | -6 |
| 15 Sept 2026, 15:58 | 14,875 | +5 |
| 13 Sept 2026, 22:20 | 14,870 | +4 |
| 12 Sept 2026, 02:00 | 14,866 | -5 |
| 9 Sept 2026, 15:19 | 14,871 | +31 |
| 6 Sept 2026, 08:41 | 14,840 | +93 |
| 3 Sept 2026, 22:21 | 14,747 | +130 |
| 2 Sept 2026, 11:04 | 14,617 | +57 |
| 1 Sept 2026, 09:47 | 14,560 | -7 |
| 31 Aug 2026, 09:17 | 14,567 | +5 |
| 30 Aug 2026, 12:05 | 14,562 | -4 |
| 29 Aug 2026, 09:48 | 14,566 | +6 |
| 28 Aug 2026, 08:48 | 14,560 | -11 |
| 27 Aug 2026, 11:38 | 14,571 | -5 |
| 26 Aug 2026, 08:03 | 14,576 | +8 |
| 25 Aug 2026, 06:12 | 14,568 | +5 |
| 24 Aug 2026, 07:35 | 14,563 | +9 |
| 22 Aug 2026, 16:56 | 14,554 | -26 |
| 21 Aug 2026, 10:48 | 14,580 | -1 |
| 20 Aug 2026, 13:47 | 14,581 | first reading |
31 posts held, back to 25 June 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 53 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.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 31 (25 June 2026 – 31 August 2026) |
| Views total | 77,390 |
| Reactions total | 4,264 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 18:27 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.
Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
13,985 reactions across 31 posts, in 4 distinct kinds. The most used accounts for 35.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5330558832475147629 | 4,975 | 35.6% | |
| custom 5215200065353694682 | 4,168 | 29.8% | |
| custom 5330257128202480104 | 2,605 | 18.6% | |
| custom 5330427762958179738 | 2,237 | 16.0% |
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 31 of the 31 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 13,985 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 25 June 2026 to 31 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hollyavele. 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 31 most recent posts we hold for this entry, published 25 June 2026 to 31 August 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.
Жду потом ваши комментарии после прослушивания о том как вам такой формат работ. На первый раз постарался сделать лайтовый хоррор. 😜
custom 5330558832475147629190custom 533042776295817973851custom 533025712820248010419custom 52152000653536946823
𓍯𓏵𓏵✦•┈๑🅂🄵🅆๑┈•✦𓏵𓏵| 𓏵 ЛЕСНАЯ ГЛУХОМАНЬ 🤩🤩🤩🤩🤩🤩🤩🤩 🐙🐙🐙🐙🐙🐙 𓏵 🄿🄰🄸🅁🄸🄽🄶: #кевдрю 𓏵 🅃🄰🄶🅂: #озвучка #хорророзвучка #ври #лисы 𓏵 🄿🄴🅁🅂🄾🄽🅂: #Эндрю #Кевин 𓏵 𓍯𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵| |─୨🄳🄴🅂🄲🅁🄸🄿🅃🄸🄾🄽ৎ─| |𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵| Пᴀᴩни ᴨᴩᴏᴄᴛᴏ хᴏᴛᴇᴧи ᴏᴛдᴏхнуᴛь, ᴨᴩᴏʙᴇᴄᴛи нᴇᴄᴋᴏᴧьᴋᴏ нᴏчᴇй ʙ ᴧᴇᴄнᴏʍ дᴏʍиᴋᴇ... Нᴏ ʙᴏᴛ ᴏни ужᴇ ᴋᴏᴛᴏᴩый ᴩᴀɜ ᴨᴩᴏᴇɜжᴀюᴛ ʍиʍᴏ ᴏднᴏᴦᴏ и ᴛᴏᴦᴏ жᴇ ᴨня, ᴀ ɯᴏᴩᴏхи ᴄᴛᴀᴧи ʙᴄᴇ бᴧижᴇ и ᴏᴛчёᴛᴧиʙᴇᴇ.
custom 5215200065353694682296custom 533055883247514762955custom 533042776295817973848custom 53302571282024801048
Пахнет второй частью?)))
custom 5215200065353694682348custom 533055883247514762961custom 533025712820248010441custom 533042776295817973815
𓍯𓏵𓏵✦•┈๑🄽🅂🄵🅆๑┈•✦𓏵𓏵| 𓏵 🄿🄰🄸🅁🄸🄽🄶: #хайтаницест 𓏵 🅃🄰🄶🅂: #озвучка #коллаб #токийскиемстители 𓏵 🄿🄴🅁🅂🄾🄽🅂: #Ран #Риндо 𓏵 •🎀•꒷꒦︶꒷꒦︶•🎀•꒷꒦︶꒷꒦︶•🎀• 🅂🄲🅁🄴🄴🄽🅆🅁🄸🅃🄴🅁: @ominae543880 🅅🄾🄸🄲🄴 🄰🄲🅃🄸🄽🄶: • Риндо — Авэль • Ран — Дан-муженёк •🎀•꒷꒦︶꒷꒦︶•🎀•꒷꒦︶꒷꒦︶•🎀•
custom 5215200065353694682393custom 533055883247514762978custom 533042776295817973850custom 53302571282024801046
Posted without readable text
custom 5330257128202480104194custom 533042776295817973844custom 533055883247514762928custom 521520006535369468214
|𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵| ♥️🕊♥️🕊♥️🤩♥️♥️♥️♥️🕊🕊 |𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵𓏵| ʍᴇᴛᴋи: #озвучка #ври #монолог #SFW #мистика #озвучкапофф #рико Фанфик: https://ficbook.net/readfic/01989478-eb98-7d86-8844-d01746a2d93b/ ТТ автора: @cutedevileva После смерти Рико стал Вороном. Настало время переосмыслить собственную жизнь и осознать ошибки. Получив возможность встретиться во снах с людьми что были важны в его жизни перед Рико появляется выбор:…
custom 5215200065353694682253custom 533055883247514762961custom 533025712820248010432custom 533042776295817973813
𓍯𓏵𓏵✦•┈๑🅂🄵🅆๑┈•✦𓏵𓏵| 𓏵 «— Поэтому мы и сложили тебя в позу для йоги.» 𓏵 𓏵 🄿🄰🄸🅁🄸🄽🄶: #кендрилы 𓏵 🅃🄰🄶🅂: #озвучка #ври #лисы 𓏵 #флафф 𓏵 🄿🄴🅁🅂🄾🄽🅂: #Эндрю #Кевин #Нил
custom 5330558832475147629496custom 5330427762958179738101custom 533025712820248010459custom 521520006535369468235
𓍯𓏵𓏵✦•┈๑🄽🅂🄵🅆๑┈•✦𓏵𓏵| 𓏵 «— Ты всегда себя так ведёшь, когда хочешь, чтобы тебя...» 𓏵 𓏵 🄿🄰🄸🅁🄸🄽🄶: #твиньярды 𓏵 🅃🄰🄶🅂: #озвучка #ври #лисы 𓏵 #ревность #неканон 𓏵 #твинцест 𓏵 🄿🄴🅁🅂🄾🄽🅂: #Аарон #Эндрю
custom 5215200065353694682367custom 533055883247514762979custom 533042776295817973854custom 53302571282024801049
Ах да, ещё раз предупреждаю. На моём канале бан будут получать все кто хоть раз будет упоминать агрессию/ненависть ко мне, к моей аудитории, к пейрингам из всех фд.
custom 5330558832475147629290custom 533042776295817973869custom 533025712820248010433custom 521520006535369468212
Posted without readable text
custom 5215200065353694682276custom 533042776295817973847custom 533055883247514762931custom 53302571282024801045
И так, мои дорогие. Опять, как пластинка, одна и та же тема. Я даже на канале оставил пост с тем, чтобы брали работы с отметкой. При том, что слив работы идёт именно с тгк, где человек подписан, а значит эта информация была любезно пропущена нахуй мимо ушей. Так вот. Мне вам запретить скачивание, копирование и прочее? Или что? Или все работы сделать платными? У меня нет ни желания, ни времени спорить с каждым, кто…
custom 5330257128202480104424custom 533055883247514762978custom 533042776295817973848custom 521520006535369468224
Voice message, posted without a caption
custom 5330257128202480104208custom 521520006535369468286custom 533055883247514762938custom 53304277629581797388
Showing the 12 most recent of 31 posts we hold for @hollyavele. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
По ком хотите следующий большой коллаб с муженьком?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 31 most recent posts we hold, published 25 June 2026 to 31 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 4 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.
@hollyavele named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“𐍅 𑀗ɞꤎተ꤀꤅꤀ 𐌏ተꤟꤌ.🎀” (@hollyavele), 14,869 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hollyavele.
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.