Channel
@amorantKf
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
294subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002269615015 |
|---|---|
| Type | Channel |
| Username | @amorantKf |
| Created | 4 February 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/amorantKf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 00:08 | 294 | +14 |
| 15 Aug 2026, 10:18 | 280 | -8 |
| 8 Aug 2026, 08:18 | 288 | no change |
| 7 Aug 2026, 21:01 | 288 | -3 |
| 7 Aug 2026, 14:55 | 291 | first reading |
4 posts held, back to 4 February 2025 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
192 reactions across 3 posts, in 13 distinct kinds. The most used accounts for 53.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 102 | 53.1% | |
| custom 5381844955352298280 | 24 | 12.5% | |
| custom 5280510935784509469 | 18 | 9.38% | |
| custom 5215543224650715137 | 11 | 5.73% | |
| custom 5217849274196324122 | 10 | 5.21% | |
| custom 5215626761764622617 | 6 | 3.13% | |
| custom 5231377725394014552 | 5 | 2.60% | |
| custom 5231104466689740800 | 4 | 2.08% | |
| custom 5280825726822536602 | 3 | 1.56% | |
| custom 5292146221232703925 | 3 | 1.56% | |
| custom 5276027750136712055 | 2 | 1.04% | |
| custom 5278473665292302343 | 2 | 1.04% | |
| custom 5298742801373103914 | 2 | 1.04% |
Custom emoji. 12 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 3 of the 4 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 192reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 4 February 2025 to 21 July 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.
@podslyshaAmorant_bot - подслушка аморанта @podsleshaAmoranta - канал подслушки
custom 52155432246507151375custom 52156267617646226172custom 52311044666897408002custom 52784736652923023432
Signed افتدى من قبلكMR
гайсы. напоминаю, что у нас есть инициалы (по желанию). Угомон словили, никто заставлять вас их ставить не будет, но если есть желание: Amrt / Amo
custom 52313777253940145525custom 52155432246507151373custom 52156267617646226173custom 52311044666897408002
Signed dv افتدى من قبلك
⭐️⭐️⭐️ 𝑪𝑯𝑨𝑻🌙 ⭐️ ⭐️Конференция Amorant для персон ⭐️Скз. Нотвирт и другое летят мимо ⛔ ⭐️ ⭐️ ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️👹𝐀𝐃𝐌𝐈𝐍𝐈𝐒𝐓𝐑𝐀𝐓𝐈𝐎𝐍 👹 𝐓𝐈𝐊𝐓𝐎𝐊 👹 𝐑𝐄𝐒𝐓 👹 𝐏𝐀𝐓𝐄𝐍𝐓 👹 𝐑𝐔𝐋𝐄𝐒
🔥102custom 538184495535229828024custom 528051093578450946918custom 521784927419632412210custom 52155432246507151373custom 52808257268225366023custom 52921462212327039253custom 52760277501367120552
Channel created
Showing the 4 most recent of 4 posts we hold for @amorantKf. 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.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“𝐀𝐌𝐎𝐑𝐀𝐍𝐓” (@amorantKf), 294 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/amorantKf.
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.