Telegram RegisterThe public register of Telegram
Telegram profile photo for Архив꩜‘ .𝑳𝒆𝒆 𝑯𝒂𝒏-𝒖𝒍

Channel

Архив꩜‘ .𝑳𝒆𝒆 𝑯𝒂𝒏-𝒖𝒍

@mantis_lee

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

32subscribers

-2 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003795166021
TypeChannel
Username@mantis_lee
CreatedBetween 1 February 2026 and 13 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live3 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/mantis_lee

Growth

32343311 August 2026 — 34 subscribers11 August 2026 — 34 subscribers3 September 2026 — 32 subscribers11 August 20263 September 2026
3 measurements spanning 23 days, net -2. 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”. The vertical axis spans 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 11:3732-2
11 Aug 2026, 16:3834no change
11 Aug 2026, 00:4634first reading

Engagement

20 posts held, back to 13 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 1 page of 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 20 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

43 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 20.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5188489844128508913920.9%
custom 5219717271437467988920.9%
custom 5373246091523290994818.6%
😢49.30%
custom 543155530197317700936.98%
custom 518864200622986992324.65%
custom 522698804547920966224.65%
custom 522876404452087349424.65%
custom 533704178066577211824.65%
🔥24.65%

Custom emoji. 8 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 9 of the 20 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 43 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 July 2026 to 25 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.

Recent posts

23 Jul 2026, 17:22 UTCviews —

Channel name was changed to «rest ꩜‘ .𝑳𝒆𝒆 𝑯𝒂𝒏-𝒖𝒍»

23 Jul 2026, 17:22 UTC38 views4 reactionsread 11 August 2026

Эйй, привет.🤷‍♂ думаю, ненадолго возьму рест, на ☺️☺️☺️☺️☺️☺️☺️☺️ или две, ну так, по своим причинам. 🌟 Не скучайте без меня:)

😢4

22 Jul 2026, 14:23 UTC30 viewsread 11 August 2026
Forwarded from @se0moonjoPhoto

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 ➿➿➿ 😀😀😀🔤🔤🔤🔤🔤🔤 вы ⳅ𐔤ⳝⲏ𐔖ᥱ забøлевăнuе 🌟 🅰️🅰️🅰️🅰️🅰️🅰️🅰️ 𝖮𝟣. 🔤ыть присоединённым к моему каналу. 𝖮𝟤. 🔤тшнуть данный пост в свõй бл0г. 𝖮𝟥. 🔤тметиться в комментариях. (🔤ожно любым, стикером, словом, просто точкой и т.д.) 🔤🔤❤️❤️ 🔠 интерактиве могут участвовать только блоги. 4⃣ℹ️8⃣ ➖➖➖➖➖

20 Jul 2026, 16:32 UTC91 views2 reactionsread 11 August 2026

⭐⭐▪️▶️🔢🔢 Кн, вп? ☺️

custom 52197172714374679882

19 Jul 2026, 16:42 UTC64 views5 reactionsread 11 August 2026

Надеюсь, теперь Сын-Так не будет злиться.

custom 51884898441285089132custom 52197172714374679881custom 53732460915232909941custom 54315553019731770091

19 Jul 2026, 16:24 UTC49 views2 reactionsread 11 August 2026

Не, ну ☺️☺️☺️☺️☺️ быть?:) На обои очень нужно. 🚔

🔥2

19 Jul 2026, 08:36 UTC37 views5 reactionsread 11 August 2026
Forwarded from @leekangsoonew

🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤 Вы как 🚬 🖤🖤🔹🖤 . 🥩 💴 Ядан ("yadang" 야당) - информатор или осведомитель. На сколько процентов ваш персонаж стукач. ☁️☁️☁️☁️☁️☁️☁️ ♾️Подписка на блог ♾️Написать в коммент любое слово - от этого зависит результат ♾️Репостнуть к себе ♾️Ждать результата .: ✨ ʏчᴀствʏют только ҕлоrи ♾️♾️♾️♾️

custom 52197172714374679883custom 52287640445208734941custom 53732460915232909941

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

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 1 registered channel — 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.

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

“Архив꩜‘ .𝑳𝒆𝒆 𝑯𝒂𝒏-𝒖𝒍” (@mantis_lee), 32 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/mantis_lee.

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.