Telegram RegisterThe public register of Telegram
Telegram profile photo for Новости | Lux × Coins

Channel

Новости | Lux × Coins

@luxcoins_news

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

957subscribers

+733 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-1003931935830
TypeChannel
Username@luxcoins_news
CreatedBetween 1 April 2026 and 20 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/luxcoins_news

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

2219575897 August 2026 — 224 subscribers8 August 2026 — 221 subscribers8 August 2026 — 221 subscribers16 August 2026 — 336 subscribers23 August 2026 — 445 subscribers29 August 2026 — 471 subscribers6 September 2026 — 851 subscribers14 September 2026 — 957 subscribers7 August 202614 September 2026
8 measurements spanning 37 days, net +733. 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 111–1,067 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 05:37957+106
6 Sept 2026, 05:56851+380
29 Aug 2026, 19:07471+26
23 Aug 2026, 13:18445+109
16 Aug 2026, 14:56336+115
8 Aug 2026, 10:33221no change
8 Aug 2026, 06:23221-3
7 Aug 2026, 21:46224first reading

Engagement

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

Reaction mix

30 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 46.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53234666131088110381446.7%
custom 5323578320913211046930.0%
custom 5325515703351025587516.7%
custom 532362240875250711013.33%
custom 532605374249412887013.33%

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 6 of the 20 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 20 most recent posts we hold, published 20 July 2026 to 4 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

4 Aug 2026, 14:23 UTC22 views3 reactionsread 8 August 2026
Poll

Начало на 20 голосов положительного ответа

  1. Да, давайте94%
  2. Не, не хочется конкурса18%

The shares total 112%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

custom 53234666131088110383

4 Aug 2026, 14:04 UTC40 views8 reactionsread 8 August 2026

📢 Как вам такая идея? Хотите конкурс с призами? 🧸✨ Планируем провести 3-дневный конкурс, в котором разыграем 5 мишек по 15⭐. Подарки могут быть: • 🎁 от имени бота — такой подарок нельзя обменять; • 🎁 от имени администратора — такой подарок можно обменять. Напишите в комментариях, хотели бы вы поучаствовать в таком конкурсе. Если интерес будет высоким — запустим его совсем скоро! 🚀

custom 53234666131088110384custom 53235783209132110462custom 53236224087525071101custom 53255157033510255871

3 Aug 2026, 17:38 UTC26 views6 reactionsread 8 August 2026

🚀 Отличные новости! Уже совсем скоро — ориентировочно завтра или послезавтра — мы запускаем новую постоянную акцию! 🎁 Каждый день среди самых активных пользователей будут разыгрываться подарки стоимостью 15⭐, 25⭐, а иногда — 50⭐ и даже 100⭐! Проявляйте активность, общайтесь, участвуйте в жизни проекта и повышайте свои шансы на получение ценных подарков. Это будет постоянная акция, поэтому возможность выиграть поя…

custom 53234666131088110384custom 53255157033510255872

2 Aug 2026, 18:09 UTC64 views13 reactionsread 8 August 2026

👨‍💻 Отличные новости! Мы наконец-то реализовали систему автоматического резервного копирования базы данных. 🎉 Теперь каждые 2 часа бот автоматически создает свежий бэкап базы данных, благодаря чему ваш прогресс, достижения и другие важные данные будут надежно защищены. Это значительно повышает надежность проекта и помогает избежать потери данных даже в непредвиденных ситуациях. Спасибо, что остаетесь с нами! 🥰

custom 53235783209132110467custom 53234666131088110383custom 53255157033510255872custom 53260537424941288701

1 Aug 2026, 10:52 UTC48 viewsread 8 August 2026

🎟️ Промокод: #AUGUST ⚖️ Сумма каждой активации: 4 000 LUX Промокод нужно активировать именно в группе. • Наш игровой чат: @Lux_GameChat

28 Jul 2026, 22:09 UTC73 views0 reactionsread 8 August 2026

🎟️ Промокод: #NFT_GIFT ⚖️ Сумма каждой активации: 4 000 LUX Промокод нужно активировать именно в группе. • Наш игровой чат: @Lux_GameChat

25 Jul 2026, 12:12 UTC80 viewsread 8 August 2026

🎉 Итоги реферального розыгрыша! Друзья, наш реферальный конкурс завершён! Спасибо всем, кто приглашал друзей и помогал развивать наш проект 🚀 🏆 Победителями становятся: • 1 место: @corooru - 650к люксов + Vice Cream #97035 ⭐ • 2 место: @helperenko - 550к люксов • 3 место: @tiret0 - 450к люксов Они пригласили наибольшее количество пользователей в нашего бота и получают подарки 🎁 ❤️ Следите за новостями и оставайт…

25 Jul 2026, 12:11 UTC47 viewsread 8 August 2026

❗️ Друзья, приносим свои искренние извинения. К сожалению, мы не подвели итоги конкурса вовремя. Это полностью наша ошибка, и мы понимаем, что многие из вас ждали результатов. Чтобы подобная ситуация больше никогда не повторилась, мы приняли решение полностью автоматизировать проведение всех конкурсов в боте. Начиная с этого момента, каждый конкурс будет запускаться, завершаться и подводить итоги автоматически, без…

24 Jul 2026, 12:52 UTC58 viewsread 8 August 2026

Через некоторое время бот будет выключен на время, мы покупаем новый хостинг, бот будет работать в разы быстрее 🏕

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Aug 2026, 14:23 UTCAnonymous Poll17 voters

Начало на 20 голосов положительного ответа

  1. Да, давайте94%
  2. Не, не хочется конкурса18%

The shares total 112%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 20 July 2026 to 4 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“Новости | Lux × Coins” (@luxcoins_news), 957 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/luxcoins_news.

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.