Telegram RegisterThe public register of Telegram
Telegram profile photo for Lena Lux 🐈‍⬛

Channel

Lena Lux 🐈‍⬛

@lenalux

Not marked by Telegram, checked 28 September 2026

On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

101subscribers

-1 since we began measuring on 19 September 2026

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

Register entry

Telegram ID-1002173420171
TypeChannel
Username@lenalux
CreatedBetween 1 June 2024 and 29 July 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live21 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 21 October 2026
On Telegramt.me/lenalux

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 79% 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

101102101.519 September 2026 — 102 subscribers19 September 2026 — 102 subscribers14 October 2026 — 101 subscribers19 September 202614 October 2026
3 measurements spanning 25 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 101–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 21:21101-1
19 Sept 2026, 14:22102no change
19 Sept 2026, 13:47102first reading

Engagement

7 posts held, back to 29 July 2024 — 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 7 posts for this entry, the most recent from 1 November 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

245 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 34.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8434.3%
custom 54157546799319083854518.4%
custom 54384570266550427074217.1%
custom 54227691475052927043514.3%
custom 5848098264179545059104.08%
custom 529644807336127838493.67%
custom 525161254898108359183.27%
custom 534840917611880254452.04%
💅52.04%
custom 534850269903167071720.816%

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

Measured over the 7 most recent posts we hold, published 29 July 2024 to 1 November 2024, 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

1 Nov 2024, 12:48 UTC≈1,210 views14 reactionsread 19 September 2026

Если у вас накопились образы, то скидывайте, буду разбирать 💋

❤14

1 Nov 2024, 12:47 UTC≈1,200 views22 reactionsread 19 September 2026
Photo

Друзья! Всем привет. Меня очень долго не было в канале, я была в «неактивной» фазе так сказать. Сначала я много работала, потом была в состоянии выгорания, дальше началась сессия 🫠 а потом я нашла для себя новое хобби. Это занятие свечами 🕯️ решила себя в этом попробовать и мне безумно понравилось 🥰 сейчас начала делать новогоднюю коллекцию. Силы и желание творить появились, так что скоро канал получит второе дыхание

❤22

16 Sept 2024, 16:32 UTC≈1,310 views62 reactionsread 19 September 2026
Photo

Кардиган Brunello Cucinelli Меховые балетки TOD’S 💔

custom 543845702665504270733custom 541575467993190838513custom 584809826417954505910❤6

9 Aug 2024, 06:26 UTC≈1,160 views52 reactionsread 19 September 2026
Photo

#образы

custom 541575467993190838526custom 52964480733612783849custom 54384570266550427079custom 54227691475052927046custom 53485026990316707172

4 Aug 2024, 11:03 UTC838 views33 reactionsread 19 September 2026
Photo

#образы

❤22custom 542276914750529270411

3 Aug 2024, 06:37 UTC868 views33 reactionsread 19 September 2026
Photo

🩵 #образы

❤20custom 52516125489810835918💅5

29 Jul 2024, 12:54 UTC726 views29 reactionsread 19 September 2026
Photo

#образы

custom 542276914750529270418custom 54157546799319083856custom 53484091761188025445

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

КОЛОБОК
@kolobok_start · 20,105
Telegram ranks this channel #82 of 84 here — alongside 83 others — read 19 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Lena Lux 🐈‍⬛” (@lenalux), 101 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/lenalux.

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.