Telegram RegisterThe public register of Telegram

Channel

#LuxFEED™

@luxfeedpub

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

2,606subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001365260960
TypeChannel
Username@luxfeedpub
CreatedBetween 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/luxfeedpub

Growth

2,6062,6102,6086 August 2026 — 2,610 subscribers7 August 2026 — 2,609 subscribers10 August 2026 — 2,606 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net -4. 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 2,605–2,611 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:462,606-3
7 Aug 2026, 22:122,609-1
6 Aug 2026, 23:332,610first reading

Engagement

20 posts held, back to 1 March 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 31 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 28s
Average length
1m 28s

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍440.0%
330.0%
🤯220.0%
🤝110.0%

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 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 10reactions 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 1 March 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, 20:11 UTC448 viewsread 7 August 2026
Photo

🐦 Lux Moreau ↣ by @MentionLux (6.4K) happy new year 🎆 stay locked in, win more, get rugged less. see you in 2026. 💬 1 ❤️ 2 👀 29 ⌚ 4m ago ♻️ ℹ️ ✨ 👾 Run /beta off for classic 𝕏 reposts.

25 Dec 2025, 21:22 UTC410 viewsread 7 August 2026
Photo

🐦 Steve ↣ by @P3b7_ (42.7K) Be careful! ╭─ 🔗 Quoting @0xakinator 📸 🚨 Security Alert It appears that the @TrustWallet browser extension may have been compromised via a supply-chain attack in the Dec 24 update. Reports indicate that importing a seed phrase into the extension can result in immediate wallet draining. ⚠️ Do NOT use the Trust Wallet extension for now, and never import seed phrase until an official clari

12 Dec 2025, 19:46 UTC330 viewsread 7 August 2026
Forwarded from @AppleActivelyExploited

Update with a fix for an actively exploited vuln(s): iOS 26.2 and iPadOS 26.2 For: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later Released: 12 Dec 2025 Security Document

12 Dec 2025, 19:46 UTC377 views0 reactionsread 7 August 2026
Forwarded from @AppleActivelyExploited

Update with a fix for an actively exploited vuln(s): macOS Tahoe 26.2 For: macOS Tahoe Released: 12 Dec 2025 Security Document

8 Sept 2025, 17:48 UTC617 views1 reactionsread 7 August 2026

🚨TLDR - Don't sign any wallet tx's - To be extra safe, disable all wallet extensions

1

8 Sept 2025, 17:33 UTC603 viewsread 7 August 2026

🐦 Lux Moreau: tweet from P3b7_ 🔥 #1 ⋅ 45m ago 💬 30 🔁 130 ❤️ 272 👀 26K ♻️ ℹ️ ✨

22 Aug 2025, 23:50 UTC379 views2 reactionsread 7 August 2026
Forwarded from @AppleActivelyExploited

Update with a fix for an actively exploited vuln(s): iOS 18.6.2 and iPadOS 18.6.2 For: iPhone XS and later, iPad Pro 13-inch, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 7th generation and later, and iPad mini 5th generation and later Released: 20 Aug 2025 Security Document

👍2

22 Aug 2025, 23:50 UTC512 views2 reactionsread 7 August 2026
Forwarded from @AppleActivelyExploited

Update with a fix for an actively exploited vuln(s): macOS Sequoia 15.6.1 For: macOS Sequoia Released: 20 Aug 2025 Security Document

👍2

1 Aug 2025, 11:59 UTC396 views1 reactionsread 7 August 2026

🐦 Lux Moreau: tweet from officer_cia ⋅ 5h ago 💬 36 🔁 125 ❤️ 471 👀 281K ♻️ ℹ️ ✨

🤝1

26 Jul 2025, 02:51 UTC665 views2 reactionsread 7 August 2026

🐦 Lux Moreau: tweet from Pirat_Nation ⋅ 21h ago 💬 287 🔁 2K ❤️ 23K 👀 853K ♻️ ℹ️ ✨

🤯2

23 Jun 2025, 01:12 UTC440 viewsread 7 August 2026
Forwarded from @iansintel

⚠️ Cointelegraph frontend compromised. Do not interact with any pop-ups. — Link

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

Forward network

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

“#LuxFEED™” (@luxfeedpub), 2,606 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/luxfeedpub.

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.