Telegram RegisterThe public register of Telegram
Telegram profile photo for liiallien

Channel

liiallien

@liiallien

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

131subscribers

-1 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-1001627514119
TypeChannel
Username@liiallien
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/liiallien

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 92% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

127132129.57 August 2026 — 132 subscribers9 August 2026 — 132 subscribers24 August 2026 — 131 subscribers31 August 2026 — 132 subscribers9 September 2026 — 131 subscribers16 September 2026 — 127 subscribers2 October 2026 — 130 subscribers12 October 2026 — 131 subscribers1317 August 202612 October 2026
8 measurements spanning 65 days, net -1. 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 126–133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 05:00131+1
2 Oct 2026, 05:39130+3
16 Sept 2026, 21:01127-4
9 Sept 2026, 05:19131-1
31 Aug 2026, 17:36132+1
24 Aug 2026, 08:05131-1
9 Aug 2026, 00:46132no change
7 Aug 2026, 19:45132first reading

Engagement

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

What this channel posts

Video runtime
9s
Average length
9s

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.

Reaction mix

142 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 33.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52718548544011959204733.1%
custom 53372680781976307982819.7%
custom 54227545832711915242014.1%
👾1611.3%
custom 5337243352070907371139.15%
custom 5336820396576501202128.45%
custom 533706814317503373064.23%

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

Measured over the 8 most recent posts we hold, published 16 July 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.

Recent posts

6 Aug 2026, 00:41 UTC60 views19 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 527185485440119592011custom 53368203965765012026custom 53370681431750337302

5 Aug 2026, 13:10 UTC66 views11 reactionsread 9 August 2026

Рецепт печенья: Ингредиенты: 🌟Сливочное масло - 80 г 🌟Яйцо - 1 шт 🌟Сахар - 80 г 🌟Мука - 220 🌟Соль - щепотка (для баланса вкуса, но я не добавляла) 🌟Шоколад - полторы плитки (я брала милку, но можно брать любой шоколад с любыми начинками, как вам хочется) Шаги готовки: 🌟Смешиваем масло (должно быть мягким для удобного смешивания), яйцо и сахар. 🌟После в полученную массу добавляем муку порциями и перемешиваем рукам…

custom 53372680781976307985custom 52718548544011959204custom 53372433520709073712

5 Aug 2026, 12:01 UTC63 views15 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 53372680781976307989custom 52718548544011959204custom 54227545832711915242

30 Jul 2026, 16:03 UTC125 views22 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 527185485440119592015custom 54227545832711915244custom 53368203965765012023

24 Jul 2026, 14:13 UTC182 views13 reactionsread 9 August 2026
Video

Я не могу меня каждый раз разматывает с этого «неть🤗🤩😇»

custom 53372680781976307986custom 53370681431750337304👾3

24 Jul 2026, 08:03 UTC167 views17 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 53372680781976307988👾6custom 53368203965765012023

21 Jul 2026, 18:33 UTC167 views26 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 542275458327119152411custom 53372433520709073718👾7

16 Jul 2026, 09:24 UTC216 views19 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 527185485440119592013custom 53372433520709073713custom 54227545832711915243

Showing the 8 most recent of 8 posts we hold for @liiallien. 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.

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

“liiallien” (@liiallien), 131 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/liiallien.

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.