Channel
@l1m1_i
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
82subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001895328653 |
|---|---|
| Type | Channel |
| Username | @l1m1_i |
| Created | Between 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/l1m1_i |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 12:41 | 82 | -1 |
| 19 Aug 2026, 16:23 | 83 | +2 |
| 11 Aug 2026, 18:48 | 81 | no change |
| 10 Aug 2026, 19:46 | 81 | first reading |
2 posts held, back to 6 August 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 2 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
51 reactions across 2 posts, in 8 distinct kinds. The most used accounts for 29.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5350819803823107874 | 15 | 29.4% | |
| custom 5350463394551986496 | 11 | 21.6% | |
| custom 5350486338267280739 | 10 | 19.6% | |
| custom 5350623996264082224 | 8 | 15.7% | |
| custom 5350346429707612864 | 2 | 3.92% | |
| custom 5350679650450304151 | 2 | 3.92% | |
| custom 5350704131763892515 | 2 | 3.92% | |
| custom 5350295736208617383 | 1 | 1.96% |
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 2 of the 2 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 51 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 6 August 2026 to 6 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.
уже скучаю 💔
custom 53504863382672807398custom 53504633945519864965custom 53506239962640822244custom 53503464297076128641custom 53506796504503041511custom 53507041317638925151custom 53508198038231078741
3/26 ❤️🩹
custom 535081980382310787414custom 53504633945519864966custom 53506239962640822244custom 53504863382672807392custom 53502957362086173831custom 53503464297076128641custom 53506796504503041511custom 53507041317638925151
Showing the 2 most recent of 2 posts we hold for @l1m1_i. 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“lim1i” (@l1m1_i), 82 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/l1m1_i.
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.