St. Petersburg 💌
custom 544505768701437070216❤🔥6custom 53979712304038906766custom 53009775544615670274custom 53979110149623987894custom 52268482958333314311custom 52581590841625475851custom 53346513607826078451

Channel
@leemiknowtop
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
101subscribers
-1 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002115029471 |
|---|---|
| Type | Channel |
| Username | @leemiknowtop |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/leemiknowtop |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 21:19 | 101 | -1 |
| 4 Sept 2026, 02:01 | 102 | -1 |
| 19 Aug 2026, 15:29 | 103 | +1 |
| 12 Aug 2026, 07:45 | 102 | no change |
| 12 Aug 2026, 07:32 | 102 | first reading |
3 posts held, back to 14 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 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 3 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
116 reactions across 3 posts, in 11 distinct kinds. The most used accounts for 20.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💋 | 24 | 20.7% | |
| custom 5397971230403890676 | 23 | 19.8% | |
| custom 5445057687014370702 | 20 | 17.2% | |
| custom 5226848295833331431 | 18 | 15.5% | |
| custom 5397911014962398789 | 8 | 6.90% | |
| custom 5300977554461567027 | 6 | 5.17% | |
| custom 5334651360782607845 | 6 | 5.17% | |
| ❤🔥 | 6 | 5.17% | |
| custom 5258159084162547585 | 2 | 1.72% | |
| custom 5436213619207475774 | 2 | 1.72% | |
| 💘 | 1 | 0.862% |
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 3 of the 3 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 14 July 2026 to 5 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.
St. Petersburg 💌
custom 544505768701437070216❤🔥6custom 53979712304038906766custom 53009775544615670274custom 53979110149623987894custom 52268482958333314311custom 52581590841625475851custom 53346513607826078451
😉💕 Такой вот классный вышел июль🎀
custom 522684829583333143113custom 539797123040389067610💋6custom 53009775544615670272custom 53979110149623987892custom 54362136192074757742custom 54450576870143707022custom 52581590841625475851
Наглядный пример того, как правильная компания может скрасить твои дни порой даже в самом ужасном месте Девчонки из рд1 !! Вы все такие классные и интересные, спасибо что не дали мне уехать домой🙏🙏 Хоть лагерь не сказка, именно вы сделали так, что я запомню его очень надолго Искренне люблю и скучаю по каждой❤️
💋18custom 53979712304038906767custom 53346513607826078455custom 52268482958333314314custom 53979110149623987892custom 54450576870143707022💘1
Showing the 3 most recent of 3 posts we hold for @leemiknowtop. 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.
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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“mialliise” (@leemiknowtop), 101 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/leemiknowtop.
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.