Channel
@CL4IR_DE_LUN3
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
16subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003841678393 |
|---|---|
| Type | Channel |
| Username | @CL4IR_DE_LUN3 |
| Created | Between 1 February 2026 and 1 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/CL4IR_DE_LUN3 |
Ecommerce storefront — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 12:42 | 16 | +1 |
| 19 Sept 2026, 15:37 | 15 | -1 |
| 3 Sept 2026, 12:37 | 16 | -1 |
| 21 Aug 2026, 06:36 | 17 | -1 |
| 11 Aug 2026, 18:46 | 18 | no change |
| 7 Aug 2026, 19:01 | 18 | first reading |
6 posts held, back to 1 April 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 6 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
52 reactions across 4 posts, in 21 distinct kinds. The most used accounts for 9.62% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 9.62% | |
| custom 5264776220016385602 | 4 | 7.69% | |
| custom 5265119899004444613 | 4 | 7.69% | |
| custom 5314326033644687408 | 4 | 7.69% | |
| ❤🔥 | 4 | 7.69% | |
| 🍓 | 4 | 7.69% | |
| custom 5373193091626846830 | 3 | 5.77% | |
| custom 5429583529732227012 | 3 | 5.77% | |
| custom 5773882762607988786 | 3 | 5.77% | |
| custom 5242696029370865845 | 2 | 3.85% | |
| custom 5251257183387009235 | 2 | 3.85% | |
| custom 5282857272123341907 | 2 | 3.85% | |
| custom 5314449406580265094 | 2 | 3.85% | |
| custom 5343912280935399674 | 2 | 3.85% | |
| 💋 | 2 | 3.85% | |
| custom 5265163505807401223 | 1 | 1.92% | |
| custom 5402207451137199353 | 1 | 1.92% | |
| custom 5415917459192431168 | 1 | 1.92% | |
| custom 5418173966290270515 | 1 | 1.92% | |
| 💘 | 1 | 1.92% | |
| 1 further kind | 1 | 1.92% |
Custom emoji. 15 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 4 of the 6 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 52 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 1 April 2026 to 8 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.
🔆🔆🔆🔆🔆🔆 😀😀😀😀 ➖5️⃣✍️ на первый заказик ➖5️⃣✍️ постоянным клиентам (3+ заказов) ➕5️⃣круток в подарок при заказе от 300⭐️ ➕3️⃣ крутки в честь дня рождения (действует в течении трёх дней после дня рождения) важно!!- чтобы использовать акцию в честь дня рождения, нужно предоставить документ в котором видно вашу дату рождения
⬜⬜🙂🙂🙂🙂🙂🙂🙂🙂🙂 ⬜🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 ⬜⬜⬜⬜⬜⬜🎁 ⬜🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀🎀 прайс Яэ Мико ⬜⬜⬜⬜⬜⬜прайс Райдэн ⬜отзывы Яэ Мико ⬜⬜⬜⬜отзывы Райдэн ⬜реклама ⬜⬜⬜⬜знакомство с Райдэн ⬜⬜⬜#райдэн #яэмико
custom 52647762200163856022custom 52651198990044446132custom 53731930916268468302custom 52512571833870092351custom 53143260336446874081custom 53144494065802650941custom 53439122809353996741custom 57738827626079887861
👛🎀🎀🩵🩵🩵🩵🩵🩵🎀🎀👛 ⬜⬜⬜⬜🔤риветствую!! ⬜⬜🎀🎀🔤i🔤🔤ae🎀🎀 ⬜⬜⬜⬜⬜⬜🎁 ⬜⬜⬜⬜🔤очему мы ? ? честно скажу, никто не обязан выбирать нас. но многие нас выбирают за то, насколько мы быстро и эффективно выполняем вашу работу . . у нас настоящие отзывы, доказательства, фотки до и после ! ! мы гарантируем безопасность вашего аккаунта, и выполняем заказы за звёзды/нфт/подарки и прочее. ⬜⬜⬜⬜🔤онкурсы ! ! госпожа Райден и Мико будут пров…
custom 53143260336446874083custom 52651198990044446132custom 57738827626079887862custom 52512571833870092351custom 52647762200163856021custom 53144494065802650941custom 53439122809353996741custom 53731930916268468301
😀🙂🙂🙂🙂🙂🙂😀 ⲡⲟⲇ эⲧυⲙ ⲡⲟⲥⲧⲟⲙ ⲃы ⲙⲟⲯⲉⲧⲉ ⲡⲟⲥⲙⲟⲧⲣⲉⲧь ⲣⲉⳅⲩⲗьⲧⲁⲧы ⲙⲟυⲭ ⳅⲁⲕⲁⳅⲟⲃ ♡ 😀😀ⳡⲧⲟ я ⲡⲟⲕⲁⳅыⲃⲁю: — ⲥⲕⲣυⲏы ⲇⲟ/ⲡⲟⲥⲗⲉ — ⲃыⲡⲁⲃⲱυⲉ ⲡⲉⲣⲥⲟⲏⲁⲯυ/ⲟⲣⲩⲯυⲉ — ⲡⲣⲟⲅⲣⲉⲥⲥ ⲁⲕⲕⲁⲩⲏⲧⲁ — ⲟⲧⳅыⲃы ⲕⲗυⲉⲏⲧⲟⲃ 😀😀ⲡⲟⳡⲉⲙⲩ ⲙⲏⲉ ⲙⲟⲯⲏⲟ ⲇⲟⲃⲉⲣяⲧь: • ⲏⲉ ⳅⲁⲭⲟⲯⲩ ⳝⲉⳅ ⲣⲁⳅⲣⲉⲱⲉⲏυя • ⲏⲉ ⲧⲣⲟⲅⲁю ⲗυⲱⲏⲉⲅⲟ ⲏⲁ ⲁⲕⲕⲁⲩⲏⲧⲉ • ⲃⲥё ⲇⲉⲗⲁю ⲁⲕⲕⲩⲣⲁⲧⲏⲟ υ ⳡⲉⲥⲧⲏⲟ • ⲡⲣυ ⲏⲉⲟⳝⲭⲟⲇυⲙⲟⲥⲧυ ⲟⲧⲡⲣⲁⲃⲗяю ⲡⲣⲟцⲉⲥⲥ ⲉⲥⲗυ ⲃы ⲩⲯⲉ ⳅⲁⲕⲁⳅыⲃⲁⲗυ ⲩ ⲙⲉⲏя — ⳝⲩⲇⲩ ⲣⲁⲇⲁ ⲟⲧⳅыⲃⲩ ⲃ ⲕⲟⲙⲙⲉⲏⲧⲁⲣυяⲭ 😀😀😀😀 #ЯэМико написать
custom 54295835297322270123❤2custom 52828572721233419072🍓1💋1💘1🕊1custom 52426960293708658451
Sticker, posted without a caption
🌟🌟🌟🌟🌟 крутки💫(цена за одну) 🎀1-25 рп— 3⭐️ 🎀26-50рп— 5⭐️ 🎀51-60рп— 7⭐️ так же цена может меняться в зависимости от вашего контента и дедлайна 💙💙💙💙💙💙💙💙 зачистка карты 💙на 100%— 300⭐️ хребет— 200⭐️ пик ветров— 125⭐️ храм пространства —150⭐️ ⚪️анемокулы— 125⭐️ 💎багровые агаты— 100⭐️ 💙 на 100%— 350⭐️ разлом— 225⭐️ долина ченьюй— 125⭐️ 🟡геокулы— 200⭐️ духовные карпы—150⭐️ 💙на 100%— 475⭐️ энканомия— 350⭐️ 🟣электрокулы— …
❤🔥4❤3🍓3💋1custom 52426960293708658451custom 52647762200163856021custom 52651635058074012231
Showing the 6 most recent of 6 posts we hold for @CL4IR_DE_LUN3. 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.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“ℳ𝒾𝓀ℴ'𝓈 sɦ᧐ρ.” (@CL4IR_DE_LUN3), 16 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/CL4IR_DE_LUN3.
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.