Telegram RegisterThe public register of Telegram
Telegram profile photo for In Core

Channel

In Core

@LuxInCore

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

86subscribers

-3 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-1002172433582
TypeChannel
Username@LuxInCore
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/LuxInCore

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

868987.57 August 2026 — 89 subscribers9 August 2026 — 89 subscribers30 August 2026 — 88 subscribers17 September 2026 — 87 subscribers12 October 2026 — 86 subscribers7 August 202612 October 2026
5 measurements spanning 66 days, net -3. 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 86–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 20:0986-1
17 Sept 2026, 18:1887-1
30 Aug 2026, 21:5488-1
9 Aug 2026, 15:1589no change
7 Aug 2026, 15:1189first reading

Engagement

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

What this channel posts

Video runtime
1m 23s
Average length
21s

Measured directly from 4 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

30 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 53.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1653.3%
custom 5355112580685775202516.7%
custom 5411420250476406699413.3%
custom 5447643901571657940310.0%
custom 526953006161830814613.33%
🤡13.33%

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

Measured over the 18 most recent posts we hold, published 24 July 2025 to 31 December 2025, 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

31 Dec 2025, 19:21 UTC164 views3 reactionsread 9 August 2026
Video

У меня уже новый, Как сами? Кто выжил, кого задело?)

❤3

11 Oct 2025, 01:22 UTC266 views4 reactionsread 9 August 2026
Video

Это всё, что вы можете, медведи?🙈

custom 54476439015716579403custom 52695300616183081461

25 Aug 2025, 22:30 UTC261 views2 reactionsread 9 August 2026

Цитата N6. Вся жизнь - крипторынок, а ты в нём альткоен 👾

custom 54114202504764066992

22 Aug 2025, 21:16 UTC262 views2 reactionsread 9 August 2026
Video

Релакс от этой вашей бычки

❤2

18 Aug 2025, 15:26 UTC184 views6 reactionsread 9 August 2026
Photo

Эльбрус - красивая история До 3856 на канатке, до 5к на квадриках Замерз дико, из еды сверху - в основе невкусные чебуреки, да и вообще толпы альпинистов шастают, но крутое, советую

❤6

13 Aug 2025, 14:08 UTC158 views4 reactionsread 9 August 2026
Photo

Я набрал в итоге пять штук, может, ещё доберу… У меня, может, взгляд замылен, или я просто именно «очень хочу» увидеть отскок по нфт, однако, учитывая, что нфт-чарты как будто бы мм-ят ботами по примеру средней руки альты, не вижу причин, почему бы всей этой «картиночной чуши» не повторить ноябрьский рывок Полное и тотальное НФА, но хочу увидеть 8–10 солан флора по этой радости

❤4

12 Aug 2025, 21:00 UTC135 views2 reactionsread 9 August 2026

Все холдеры альты будут сказочно богаты (кроме не холдеров тензора) 🤡

custom 53551125806857752022

12 Aug 2025, 17:57 UTC116 views2 reactionsread 9 August 2026

А я всегда говорил, что булишь по этх 🤡

🤡1custom 54114202504764066991

7 Aug 2025, 09:22 UTC167 views2 reactionsread 9 August 2026

Дали ~12к МЕ Стаканить не стал, стратегическое решение похолдить до 0,8$ 👾

❤1custom 54114202504764066991

5 Aug 2025, 20:56 UTC168 viewsread 9 August 2026
Video

На меня подписаны инвесторы? 👾

2 Aug 2025, 20:37 UTC173 views3 reactionsread 9 August 2026

Ну что пацаны, золотая эпоха криптовалют?🤡

custom 53551125806857752023

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

“In Core” (@LuxInCore), 86 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/LuxInCore.

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.