Channel
@leeseocutiiie
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
144subscribers
+7 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002207579689 |
|---|---|
| Type | Channel |
| Username | @leeseocutiiie |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/leeseocutiiie |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 11:59 | 144 | -1 |
| 9 Sept 2026, 15:58 | 145 | +5 |
| 24 Aug 2026, 23:17 | 140 | -2 |
| 18 Aug 2026, 06:12 | 142 | +5 |
| 9 Aug 2026, 19:00 | 137 | no change |
| 9 Aug 2026, 18:50 | 137 | first reading |
5 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 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 5 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
242 reactions across 5 posts, in 31 distinct kinds. The most used accounts for 9.50% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5451830914864687158 | 23 | 9.50% | |
| custom 5276355572105498956 | 20 | 8.26% | |
| custom 5278590595776926800 | 20 | 8.26% | |
| custom 5251395086196970738 | 17 | 7.02% | |
| custom 5264889306505321327 | 17 | 7.02% | |
| custom 5465516982772211518 | 15 | 6.20% | |
| custom 5221956912198751590 | 14 | 5.79% | |
| custom 5404562617928816079 | 14 | 5.79% | |
| custom 5357257908260209637 | 12 | 4.96% | |
| custom 5386463170476924103 | 12 | 4.96% | |
| custom 5235463678106571250 | 11 | 4.55% | |
| custom 5296657148074293727 | 11 | 4.55% | |
| custom 5301029051119466979 | 10 | 4.13% | |
| custom 5422391405131626747 | 7 | 2.89% | |
| custom 5344056703505686734 | 6 | 2.48% | |
| custom 5224693742669162014 | 4 | 1.65% | |
| custom 5244787811588002593 | 3 | 1.24% | |
| custom 5258350820092580988 | 3 | 1.24% | |
| custom 5341446162253631701 | 3 | 1.24% | |
| custom 5294018625110312716 | 2 | 0.826% | |
| 11 further kinds | 18 | 7.44% |
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 5 of the 5 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 242 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 25 June 2026 to 1 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @leeseocutiiie. 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 5 most recent posts we hold for this entry, published 25 June 2026 to 1 July 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.
🌟 以心伝心 (Ishin-denshin) — «от сéрдца к сéрдцу 🤩» 🌼🌼 ▫️
custom 526488930650532132717custom 522195691219875159014custom 523546367810657125011custom 52583508200925809883custom 53414461622536317013custom 54720559416313290362custom 54744349197216288002custom 54046257840128384461
новая эра officially started.... 😱😱 🤩
custom 546551698277221151815custom 535725790826020963712custom 530102905111946697910custom 52246937426691620144custom 53213484984471702282custom 53393219745082604622custom 54065880858508998752
🌟🌟🌟 𝚑𝚊𝚙𝚙𝚢 ✶ 𝚐𝚛𝚊𝚍𝚞𝚊𝚝𝚒𝚘𝚗 🌟 🤩
custom 527859059577692680020custom 525139508619697073817custom 538646317047692410312custom 53440567035056867346custom 52447878115880025933custom 53010682341060943152custom 52921322239342860281custom 52966890425014453391
File, posted without a caption
custom 529665714807429372710custom 52763555721054989567custom 54518309148646871585custom 54223914051316267473custom 52940186251103127161custom 54045626179288160791
𝙰𝚗𝚍 𝙸 𝚖𝚎𝚕𝚝 𝚠𝚒𝚝𝚑 𝚢𝚘𝚞, 𝚢𝚘𝚞𝚛 ❤️😖🔠 𝚊𝚗𝚍 𝚖𝚢 😄🅰️🔠☺️ !! 𝚗𝚘𝚠 𝙸 𝚜𝚎𝚎 𝚝𝚑𝚎 𝚠𝚘𝚛𝚕𝚍 𝚒𝚗.... 𝗽𝘂𝗿𝗽𝗹𝗲... 𝗽𝘂𝗿𝗽𝗹𝗲 🟪🟪 🤩
custom 545183091486468715818custom 527635557210549895613custom 540456261792881607913custom 54223914051316267474custom 54449079386846345922custom 52940186251103127161custom 52966571480742937271custom 52966615633006762721
Showing the 5 most recent of 5 posts we hold for @leeseocutiiie. 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.
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.
Named by 3 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“bad idea ✸ : right ?” (@leeseocutiiie), 144 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/leeseocutiiie.
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.