Channel
@LUKSO_News
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,186subscribers
-18 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001321489542 |
|---|---|
| Type | Channel |
| Username | @LUKSO_News |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/LUKSO_News |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 19:57 | 1,186 | -3 |
| 2 Sept 2026, 07:18 | 1,189 | -1 |
| 30 Aug 2026, 01:17 | 1,190 | -2 |
| 27 Aug 2026, 08:37 | 1,192 | -2 |
| 24 Aug 2026, 00:42 | 1,194 | -1 |
| 20 Aug 2026, 15:26 | 1,195 | -4 |
| 17 Aug 2026, 13:47 | 1,199 | -2 |
| 10 Aug 2026, 20:01 | 1,201 | -2 |
| 7 Aug 2026, 12:30 | 1,203 | -1 |
| 6 Aug 2026, 15:49 | 1,204 | first reading |
20 posts held, back to 13 May 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 22 July 2026. An engagement rate over an empty window would be a number about nothing.
385 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 48.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 186 | 48.3% | |
| ❤ | 172 | 44.7% | |
| 👍 | 13 | 3.38% | |
| 🙏 | 5 | 1.30% | |
| 😢 | 4 | 1.04% | |
| 👏 | 3 | 0.779% | |
| ❤🔥 | 1 | 0.26% | |
| 💯 | 1 | 0.26% |
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 20 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 385 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 13 May 2026 to 22 July 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.
🆙 Universal Profiles Browser Extension - Update 🆙 Universal Profiles Browser Extension 3.0.1-beta.102 is now available! ✨ What changed: • View error details when execution or gas estimation fails • Choose which profiles to include in a backup • Select which eligible controller pays for and signs a transaction • Fewer error modals and improved extension stability • Updated LYX and ETH market prices Don't have a U…
🔥30
📰 Universal Page is Closing 📰 Universal Page has been part of the LUKSO ecosystem since the first LUKSO hackathon in 2021. We want to extend our heartfelt thanks to Jake, Vlad, and everyone who poured their energy into Universal Page over the years. In that time, the team built one of the earliest marketplaces for LSP-based digital assets. If you used Universal Page, please take note: • Staked LYX: Validators ar…
👍4😢4❤2
⚠️ Security Warning: Fake LUKSO Outreach ⚠️ We are aware of scammers impersonating LUKSO representatives through fake recruitment and project opportunities, calendar invitations, and video calls. Targets may be asked to download or run a “demo” from the following GitHub repository: lukso-hub/lukso-platform This repository and GitHub organization are not affiliated with LUKSO. The repository has been reported as …
🙏5👍2❤1
🎙 LUKSO Live: Community Sync-UP 🎙 The LUKSO Community Sync-UP starts in 30 minutes. Join us for an ecosystem update and community Q&A. 🆙 ⏰ 3:20 PM UTC / 5:20 PM CEST Tune in here↴ https://www.youtube.com/watch?v=_glNqSu7WNY
❤6👍2
🎙 LUKSO Live: Community Sync-UP 🎙 Join us this Wednesday for the LUKSO Community Sync-UP! 🆙 We’ll share where things stand, discuss current priorities, and answer questions from the community. 🗓 July 15 ⏰ 3:20 PM UTC / 5:20 PM CEST Tune in here↴ https://www.youtube.com/watch?v=_glNqSu7WNY
❤19❤🔥1
LUKSO Validator Explorer Upgrade - Withdrawal Dashboard The LUKSO validator explorer has been upgraded. Validator operators can now use the new Withdrawal Dashboard to track all validators linked to a withdrawal address or withdrawal credentials. You can see active/offline status, recent participation, balances, and validator state in one place. Especially useful for operators managing multiple validators under t…
❤10
🆙 Universal Profiles Mobile - Update 🆙 Universal Profiles Mobile 1.24.0 is now live! ✨ This release adds new apps, improves collectible images, and improves how Universal Everything links work with the mobile app. What changed • UP! Store is now available in the apps list • Groov is now available in the apps list • Collectible images now load in the correct order • Universal Everything links can now open directly…
❤25
🆙 Universal Profiles Mobile - Update 🆙 Universal Profiles Mobile 1.22.1 is now live! ✨ This release cleans up a few everyday app details. What changed • The dApps list on the Home screen is now scrollable • Collectible thumbnails now use the first image from the collectible image list • Collectible balances now format correctly with decimals • The profile card now has a quick-access button for your signed QR code…
❤12🔥5
🆙 Token Creator V2 is live on Universal Everything 🆙 Token Creator V2 adds new controls for tokens connected to Universal Profiles. New options: • Non-transferable tokens • Revocable memberships and credentials • Adjustable maximum supply • Balance restrictions per Universal Profile (e.g., 1 per UP) This makes it easier to create credentials, access passes, memberships, attendance records, and contribution badges…
🔥29❤5👏2
🆙 A Suite of Applications for New Cultural Systems 🆙 Culture Studio is a suite of decentralized applications designed for communities, creators, developers, and cultural organizers building with Universal Profiles. The article by Kat Banas introduces the broader idea behind the suite: tools for participation, presence, belonging, and cultural coordination. It covers: • Token Creator • Proof of Presence • Airdrop …
❤15🔥4
🆙 Universal Profiles Mobile - Update 🆙 Universal Profiles Mobile 1.22.0 is now live. ✨ This release combines the 1.20.0 - 1.22.0 updates. Most of the work happened under the hood, giving the app a stronger foundation for faster future updates while making profiles, assets, and app screens feel faster and cleaner. What changed • Profiles and assets load faster • Images stay cached while replacements load • Creator…
🔥30❤3
🎙 Reminder: LUKSO x Lumera Livestream Today 🎙 We’re going live with Lumera today to talk about Cascade, permanent and verifiable storage, and why reliable data matters for builders on LUKSO. Join the conversation with Vincent Chui and Kaleab as we discuss what this means for NFTs, Universal Profiles, and identity-linked applications. ⏰ 11 AM EDT / 3 PM UTC / 5 PM CEST Tune in here↴ https://www.youtube.com/watch…
🔥4
Showing the 12 most recent of 20 posts we hold for @LUKSO_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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“LUKSO Announcements” (@LUKSO_News), 1,186 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/LUKSO_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.