LUWI COIN ANNOUNCEMENT π’π’ pinned a photo

Channel
LUWI COIN ANNOUNCEMENT π’π’
@LuwiCoinOfficial
On this record: Topic Β· Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Cite this entry
202subscribers
-22 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 | -1001832972783 |
|---|---|
| Type | Channel |
| Username | @LuwiCoinOfficial |
| Created | Between 1 October 2022 and 30 September 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/LuwiCoinOfficial |
Topic
Crypto & trading β 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 01:58 | 202 | -1 |
| 30 Sept 2026, 12:20 | 203 | -2 |
| 15 Sept 2026, 06:59 | 205 | -1 |
| 7 Sept 2026, 08:36 | 206 | -4 |
| 28 Aug 2026, 18:04 | 210 | -6 |
| 21 Aug 2026, 03:48 | 216 | -4 |
| 14 Aug 2026, 16:34 | 220 | -4 |
| 8 Aug 2026, 10:30 | 224 | no change |
| 7 Aug 2026, 21:56 | 224 | first reading |
Engagement
20 posts held, back to 4 January 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 20 posts for this entry, the most recent from 26 January 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 27s
- Average length
- 27s
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
121 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 71.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 87 | 71.9% | |
| β€ | 28 | 23.1% | |
| π | 3 | 2.48% | |
| π€ | 2 | 1.65% | |
| π | 1 | 0.826% |
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 5 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 121 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 4 January 2024 to 26 January 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
π Congratulations, Luwi Coin Community! π We are thrilled to announce that Luwi Coin has successfully reached the end of Round 1 sales! π Your incredible support and enthusiasm have propelled us to this milestone, and we couldn't be more grateful for each and every one of you. What's Next? Distribution and listing will commence at the end of the next round, marking the beginning of an exciting new chapter for Luwi β¦
π3
π Exciting News! π Luwi Coin is set to conquer new horizons with upcoming listings on Mexc Global Exchange, Bitmart, and Probit Global! π The listing processes are about to kick off,ππ marking a significant milestone in our journey. Stay tuned for more updates as we expand the Luwi Coin community! ππ #LuwiCoin #CryptoListing #MexcGlobal #Bitmart #ProbitGlobal #CryptocurrencyExpansion
π€2
LUWI COIN ANNOUNCEMENT π’π’ pinned a photo
π’ ANNOUNCEMENT π’π’ Dear Luwi Coin Community, We hope this message finds you well and thriving in the Luwi Coin journey. We're writing to inform you about a crucial update regarding the ongoing $15 USDT Airdrop and withdrawal procedures. Key Points: 1. Conversion Requirement: - To participate in the ongoing $15 USDT Airdrop, all users are expected to convert their USDT to Luwi Coin. 2. Airdrop Countdown: - Thβ¦
LUWI COIN ANNOUNCEMENT π’π’ pinned a photo
π MAINTENANCE COMPLETED: πβ¨ Dear Luwi Coin Community, Great news! Our maintenance is complete, and all services are now fully restored. π οΈπ If you participated in Claim.luwicoin.app, kindly create an account on our main platform at https://luwicoin.app and resubmit all Entries before the upcoming payment. Your cooperation ensures a seamless process. Thank you for your understanding and continued support. Stay tunβ¦
LUWI COIN ANNOUNCEMENT π’π’ pinned a photo
π Apology for Downtime: Payment Reschedulingπ Dear Luwi Coin Community, We sincerely apologize for the inconvenience caused by the recent downtime on our site ( https://luwicoin.app). πβ οΈ Due to this, payments have been rescheduled, and they are now set for January 21st. We understand this may impact your space, and we appreciate your understanding. Stay connected for more updates and detailed information. Your pβ¦
LUWI COIN ANNOUNCEMENT π’π’ pinned a photo
β οΈATTENTION β οΈ Dear Luwi Coin Community, Due to an overwhelming response and high traffic, our website and app are undergoing maintenance to enhance your experience. π»βοΈ We appreciate your patience and understanding during this period. Rest assured, we're working diligently to get everything back up and running smoothly. Thank you! #Luwi_Team
π3
LUWI COIN ANNOUNCEMENT π’π’ pinned a photo
Showing the 12 most recent of 20 posts we hold for @LuwiCoinOfficial. 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 10 October 2026 β this entry's latest reading, not the date you are reading this.
βLUWI COIN ANNOUNCEMENT π’π’β (@LuwiCoinOfficial), 202 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/LuwiCoinOfficial.
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.