дурацкое свойство хотелок: прибавляться, но вы только взгляните на них
custom 524896929725810436571

Channel
@afiprelude
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
1,401subscribers
+76 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001760559267 |
|---|---|
| Type | Channel |
| Username | @afiprelude |
| Created | 30 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/afiprelude |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
@afiprelude was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 22:14 | 1,401 | +40 |
| 5 Oct 2026, 01:56 | 1,361 | +7 |
| 28 Sept 2026, 07:22 | 1,354 | +30 |
| 18 Sept 2026, 13:58 | 1,324 | -4 |
| 13 Sept 2026, 21:02 | 1,328 | -2 |
| 10 Sept 2026, 12:17 | 1,330 | -1 |
| 5 Sept 2026, 05:16 | 1,331 | -6 |
| 1 Sept 2026, 18:23 | 1,337 | -9 |
| 29 Aug 2026, 21:13 | 1,346 | -1 |
| 26 Aug 2026, 23:18 | 1,347 | -7 |
| 24 Aug 2026, 02:54 | 1,354 | -3 |
| 20 Aug 2026, 10:23 | 1,357 | +50 |
| 17 Aug 2026, 10:27 | 1,307 | +1 |
| 14 Aug 2026, 03:14 | 1,306 | -10 |
| 11 Aug 2026, 06:42 | 1,316 | -6 |
| 8 Aug 2026, 06:13 | 1,322 | -3 |
| 7 Aug 2026, 22:31 | 1,325 | no change |
| 7 Aug 2026, 12:28 | 1,325 | first reading |
27 posts held, back to 16 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 2 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 25 September 2026 |
|---|---|
| Posts held | 27 (16 July 2026 – 25 September 2026) |
| Views total | 7,092 |
| Reactions total | 584 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Sept 2026, 07: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.
Measured directly from 1 video 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.
1,066 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 42.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5248969297258104365 | 449 | 42.1% | |
| custom 5429224783998900325 | 278 | 26.1% | |
| custom 5296414645630834905 | 240 | 22.5% | |
| custom 5429465203383228958 | 99 | 9.29% |
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 14 of the 27 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,066 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 16 July 2026 to 25 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.
дурацкое свойство хотелок: прибавляться, но вы только взгляните на них
custom 524896929725810436571
🤩 навела порядок (или наоборот хаос рок-н-ролл?) делитесь своими обоями
custom 524896929725810436565
u can find my soul somewhere around here: ⭐️ love spells — wish i didn’t love you 📼 henry morris — one night stand ⭐️ tv on the radio — wolf like me 📼 steve lacy — oh yeah? ⭐️ cocteau twins — cico buff 📼 cannons — fire for you ⭐️ nessa barrett — buffalo 66 📼 arctic monkeys — snap out of it
custom 524896929725810436544
🤩 veta 🧷 isfp 9w1 🖤 sun aquarius: 0902 👔 ravenclaw 🌟 inst: itsmasun ✍️ letters: cherry wine ✨ co—star: afiprelude
custom 524896929725810436564
не пугаемся, произошел небольшой ребрендинг, честно, новой эпохе давно было пора настать, уже не ассоциирую себя с никнеймом, который придумала шесть лет назад, а за новый скажем спасибо группе the clash, в честь песни которых названа глава моего любимого фанфика!
custom 524896929725810436584
home sweet home
custom 524896929725810436574
так, ну что, Я ДОМА, я снова в своей любимой обители! корея встретила безумнейшим малиновым рассветом, которые здесь из-за влажности ну очень редкие, а еще всю дорогу мы смотрели дом дракона. весь первый сезон залпом, пока, собственно, наш железный дракон не приземлился в самом родном сердцу крае. у меня адский джетлаг, но придется привыкать… мне доброго утра, а вам доброй ночи
custom 524896929725810436524
меня не отпустили, и я не отпускаюсь
custom 524896929725810436523
🍵 самое время утепляться, пить витамины и беречь себя. растерла свежую малину, добавила лимон и мёд, залила кипятком, у кого есть личные защитники иммунитета, делитесь рецептами!
custom 529641464563083490540custom 542922478399890032535
Posted without readable text
custom 542922478399890032534custom 529641464563083490526
Posted without readable text
custom 542922478399890032555custom 529641464563083490536
🎀
custom 529641464563083490579custom 542922478399890032561
Showing the 12 most recent of 27 posts we hold for @afiprelude. 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.
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.
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.
@afiprelude 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.
References a handle that is not a live channel — we have no record it ever was one.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“all the young punks” (@afiprelude), 1,401 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/afiprelude.
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.