Channel
@dailyavenpaz
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
773subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002882433234 |
|---|---|
| Type | Channel |
| Username | @dailyavenpaz |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/dailyavenpaz |
Gaming — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 14 Sept 2026, 12:56 | 773 | +6 |
| 5 Sept 2026, 23:18 | 767 | -3 |
| 27 Aug 2026, 19:47 | 770 | -2 |
| 21 Aug 2026, 13:59 | 772 | -2 |
| 14 Aug 2026, 18:29 | 774 | -9 |
| 7 Aug 2026, 07:24 | 783 | -1 |
| 6 Aug 2026, 15:35 | 784 | no change |
| 6 Aug 2026, 12:17 | 784 | first reading |
20 posts held, back to 30 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.
242 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 26.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 65 | 26.9% | |
| 💋 | 52 | 21.5% | |
| custom 5461002001481496636 | 46 | 19.0% | |
| custom 5460787807167479708 | 32 | 13.2% | |
| ❤🔥 | 18 | 7.44% | |
| 🍓 | 13 | 5.37% | |
| custom 5460961349616039958 | 7 | 2.89% | |
| 💘 | 7 | 2.89% | |
| 😍 | 2 | 0.826% |
Custom emoji. 3 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 12 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 242 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 30 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.
𝙊𝙁𝙁𝙄𝘾𝙩𝙞𝙡 . ˖ ִ 🤩 Рекв. Жарко пипец. Приходится телефон в морозилку кидать ... → #Aventurine × #Topaz (🤩) tags › #avenpaz #hsr #gluing
custom 546078780716747970819💋11custom 54610020014814966366❤5custom 54609613496160399582
Signed Rin
🤩 𝐚𝐯𝐞𝐧𝐩𝐚𝐳 daily 🌟🌟🌟 🌟 🌟 🌟 🤩🤩 🤩 #FA 🥹 𝐜𝐫𝐞𝐝𝐢𝐭 🌟🌟
❤17❤🔥11💋9💘6custom 54607878071674797082
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
🤩 𝐚𝐯𝐞𝐧𝐩𝐚𝐳 daily 🌟🌟🌟 🌟 🌟 🌟 🤩🤩 🤩 #FA 🥹 𝐜𝐫𝐞𝐝𝐢𝐭 🌟🌟
❤25custom 546100200148149663611custom 54609613496160399585💋3💘1
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
🤩 𝐚𝐯𝐞𝐧𝐩𝐚𝐳 daily 🌟🌟🌟 🌟 🌟 🌟 🤩🤩 🤩 #FA 🥹 𝐜𝐫𝐞𝐝𝐢𝐭 🌟🌟
custom 546100200148149663622🍓13💋8
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
🤩 𝐚𝐯𝐞𝐧𝐩𝐚𝐳 daily 🌟🌟🌟 🌟 🌟 🌟 🤩🤩 🤩 #FV 🥹 𝐜𝐫𝐞𝐝𝐢𝐭 🌟🌟
❤13custom 54610020014814966366💋4custom 54607878071674797083
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ㅤ ︵ׄ⏜ 𝒿𝓊𝓈𝓉 𝐚 𝐬𝐞𝐜 😻❗️ 🪦 𝐰𝐡𝐚𝐭 𝒾𝓈 𝑡ℎ𝑖𝑠 ִ ִ ⎯ׄ 🎁 noy ִ 🤩 𝐝𝐚𝐢𝐥𝐲𝑐𝑓 ۪ 𝓌𝓌 ⏝ 🪦 ㅤ ⏜ зацепил 🎁 новый ◟ 🎀 ⏝︶ статный 😻 красный альв ? ✨ 𝓉𝒽ℯℯ𝓃 ִ ִ не упускай ⏜ возможность 😻🍭₎ 𝓪𝓷𝓭 подписывайся ❗️ ᅠ⏝︶ 𝒸𝓁𝒾𝒸𝓀 ◝ 𝒸𝓁𝒾𝒸𝓀 💕
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ㅤ ︵ׄ⏜ 𝒿𝓊𝓈𝓉 𝐚 𝐬𝐞𝐜 😻❗️ 🪦 𝐰𝐡𝐚𝐭 𝒾𝓈 𝑡ℎ𝑖𝑠 ִ ִ ⎯ׄ 🎁 blade ִ 🤩 𝐝𝐚𝐢𝐥𝐲𝑐𝑓 ۪ 𝓌𝓌 ⏝ 🪦 ㅤ ⏜ полюбился 🎁 бессмертный ◟ 🎀 ⏝︶ охотник 😻 за стелларонами ? ✨ 𝓉𝒽ℯℯ𝓃 ִ ִ не упускай ⏜ возможность 😻🎁₎ 𝓪𝓷𝓭 подписывайся ❗️ ᅠ⏝︶ 𝒸𝓁𝒾𝒸𝓀 ◝ 𝒸𝓁𝒾𝒸𝓀 💕
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
🤩 𝐚𝐯𝐞𝐧𝐩𝐚𝐳 daily 🌟🌟🌟 🌟 🌟 🌟 🤩🤩 🤩 #FA 🥹 𝐜𝐫𝐞𝐝𝐢𝐭 🌟🌟
💋14❤🔥7custom 54607878071674797087❤4
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ㅤㅤ🕯 😻 𝐰𝐚𝐢𝐭 😖 ┈┈ 𝑑𝑜 𝐲𝐨𝐮 𝓵𝓸𝓿𝓮 🦴 ₎ 𝐫𝐮𝐚𝐧 𝐦𝐞𝐢😻 ⏝︶ ⏜ ֺ обожаешь жуань мэй❓◝ ◟🐈⬛ 😻 и в поиске хорошего дейли с ней❓ ⎯ׅ⎯ׄ💕 тогда ⋮ добро пожаловать к нам 🧪 ︶⏝ 𝒶𝓃𝒹 подпишись скорее 🎀😻
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ᅠᅠ.𝐁𝐋𝐀𝐂𝐊𝐒𝐖𝐀𝐍_𝐃𝐀𝐈𝐋𝐘.𝐓.𝐌𝐄.💞 Любишь хранительницу сада воспоминаний – Чёрный лебедь ? ? 💃 ᅠ😻😻Ищешь арты, эдиты и другой контент с ней ? ᅠᅠᅠ😻 ( 🤳 ) 😻 Скорее заходи к нам ! 😻
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ㅤ ︵ׄ⏜ 𝒿𝓊𝓈𝓉 𝐚 𝐬𝐞𝐜 😻❗️ 🪦 𝐰𝐡𝐚𝐭 𝒾𝓈 𝑡ℎ𝑖𝑠 ִ ִ ⎯ׄ 🎁 nihilux ִ 🤍 𝐝𝐚𝐢𝐥𝐲𝑐𝑓 ۪ 𝓌𝓌 ⏝ 🪦 ㅤ ⏜ нравится 🎁 загадочная ◟ 🤩 ⏝︶ мангака 😻 нигилюкса? ✨ 𝓉𝒽ℯℯ𝓃 ִ ִ не упускай ⏜ возможность 😻🎁₎ 𝓪𝓷𝓭 подписывайся ❗️ ᅠ⏝︶ 𝒸𝓁𝒾𝒸𝓀 ◝ 𝒸𝓁𝒾𝒸𝓀 💕
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
ㅤ ︶⏝ 𝒿𝓊𝓈𝓉 𝐚 𝐬𝐞𝐜 😻❗️ 🪦 𝐰𝐡𝐚𝐭 𝒾𝓈 𝑡ℎ𝑖𝑠 ִ ִ ⎯ׄ 🌺 kafka ִ 🤩 𝐝𝐚𝐢𝐥𝐲𝑐𝑓 ۪ 𝓌𝓌 ⏝ 🪦 ㅤ ⏜ понравилась 🎇 загадочная ◟ 🎀 ⏝︶ охотница 😻 за стелларонами ? ✨ 𝓉𝒽ℯℯ𝓃 ִ ִ не упускай ⏜ возможность 😻🐈⬛₎ 𝓪𝓷𝓭 подписывайся ❗️ ᅠ⏝︶ 𝒸𝓁𝒾𝒸𝓀 ◝ 𝒸𝓁𝒾𝒸𝓀 💕
Signed ㅤׄᅠ𝓬𝗼𝗻𝗮 ♡͡ 🔥⚔️
Showing the 12 most recent of 20 posts we hold for @dailyavenpaz. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 registered channels — 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.
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.
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.
“♡͡ㅤׄ 𝓪ven𝓅az 𝓭aily” (@dailyavenpaz), 773 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/dailyavenpaz.
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.