Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝟐𝟐

Channel

𝟐𝟐

@llusins

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry

68subscribers

-15 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002359647611
TypeChannel
Username@llusins
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live8 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/llusins

Growth

688375.57 August 2026 — 83 subscribers9 August 2026 — 83 subscribers16 August 2026 — 78 subscribers23 August 2026 — 74 subscribers29 August 2026 — 69 subscribers8 September 2026 — 68 subscribers7 August 20268 September 2026
6 measurements spanning 31 days, net -15. 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 66–85 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 00:3768-1
29 Aug 2026, 05:1269-5
23 Aug 2026, 05:1774-4
16 Aug 2026, 14:3578-5
9 Aug 2026, 17:4783no change
7 Aug 2026, 19:3483first reading

Engagement

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

What this channel posts

Video runtime
23s
Average length
12s

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.

Reaction mix

2,052 reactions across 17 posts, in 17 distinct kinds. The most used accounts for 7.89% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54048137618464931161627.89%
custom 54250459096689227491396.77%
custom 54653737413179059651366.63%
custom 51974933282365355621296.29%
custom 54160637285986667231296.29%
custom 53463138290788142391286.24%
custom 54158442257050901271276.19%
custom 52445631332588184741256.09%
custom 53482744558796328761215.90%
custom 54364031990639177981215.90%
custom 53484748504637318951205.85%
custom 54631041560446483051205.85%
custom 52494940649522695781125.46%
custom 52268167364136438141085.26%
custom 51972607600524252061075.21%
custom 5348355549157148439924.48%
custom 5436136515954574611763.70%

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 17 of the 17 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 2,052 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 25 May 2026 to 25 June 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.

Telegram Stars

Stars received
1,039
across the posts below
Posts paid on
17
of 17 we hold a reading for · 100%
Most on one post
660
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @llusins. 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 17 most recent posts we hold for this entry, published 25 May 2026 to 25 June 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.

Recent posts

18 Jun 2026, 21:09 UTC472 views125 reactions29 Starsread 9 August 2026
Photo

Photo, posted without a caption

custom 5244563133258818474125

8 Jun 2026, 14:16 UTC600 views129 reactions23 Starsread 9 August 2026
Photo

🐈‍⬛

custom 5197493328236535562129

5 Jun 2026, 21:19 UTC586 views128 reactions22 Starsread 9 August 2026
Photo

🤩

custom 5346313829078814239128

2 Jun 2026, 21:31 UTC661 views136 reactions22 Starsread 9 August 2026
Photo

🐱

custom 5465373741317905965136

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

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

“𝟐𝟐” (@llusins), 68 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/llusins.

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.