Channel
@AZURA_INFO
On this record: Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Cite this entry
78subscribers
+37 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002472975103 |
|---|---|
| Type | Channel |
| Username | @AZURA_INFO |
| Created | 7 February 2025 โ measured โ dated from the channelโs first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/AZURA_INFO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 02:25 | 78 | +7 |
| 21 Aug 2026, 15:28 | 71 | +11 |
| 14 Aug 2026, 13:57 | 60 | +20 |
| 10 Aug 2026, 19:02 | 40 | no change |
| 7 Aug 2026, 09:40 | 40 | -1 |
| 6 Aug 2026, 20:04 | 41 | first reading |
3 posts held, back to 7 February 2025 โ 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 3 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.
2,533 reactions across 1 post, in 11 distinct kinds. The most used accounts for 28.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ฅ | 715 | 28.2% | |
| ๐ฏ | 703 | 27.8% | |
| โคโ๐ฅ | 635 | 25.1% | |
| ๐ป | 120 | 4.74% | |
| โค | 105 | 4.15% | |
| ๐ | 79 | 3.12% | |
| ๐ | 69 | 2.72% | |
| ๐ | 55 | 2.17% | |
| ๐ณ | 36 | 1.42% | |
| โก | 13 | 0.513% | |
| ๐ | 3 | 0.118% |
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 1 of the 3 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 2,533 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 3 most recent posts we hold, published 7 February 2025 to 23 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.
๐ผ๐๐๐๐ผ ๐ฝ๐๐ pinned ยซโญโ โฆ ๐๐๐ข๐จ๐ง ๐ ๐ โ ๐ค Name Amirali โ ๐ฌ Occupation Video Editor โ ๐ Location Iran ๐ฎ๐ท โ ๐ฃ๏ธ Languages Persian โข English โ ๐ป Learning After Effects & Programming โ ๐ง Hobbies Music โข Fitness โข Swimming โฐโโโโโโโโโโโโโ โญโ โฆ ๐ ๐ฌ ๐๐ข๐ง๐ฆ โAZURA AE BOTโจโฆยป
โญโ โฆ ๐๐๐ข๐จ๐ง ๐ ๐ โ ๐ค Name Amirali โ ๐ฌ Occupation Video Editor โ ๐ Location Iran ๐ฎ๐ท โ ๐ฃ๏ธ Languages Persian โข English โ ๐ป Learning After Effects & Programming โ ๐ง Hobbies Music โข Fitness โข Swimming โฐโโโโโโโโโโโโโ โญโ โฆ ๐ ๐ฌ ๐๐ข๐ง๐ฆ โAZURA AE BOTโจ โ@aefileebot โAZURA EDIT BOT๐ฅ โ@AZURA_EDIT_UPLOADER_bot โฐโโโโโโโโโโโโโ โญโ โฆ ๐ฆ๐ข๐๐๐๐๐ฆ โ ๐ข Telegram โ AZURA EDIT & AZURA AE โฐโโโโโโโโโโโโโ โฆ "Create. Improve. Repea
๐ฅ715๐ฏ703โคโ๐ฅ635๐ป120โค105๐79๐69๐55
Channel created
Showing the 3 most recent of 3 posts we hold for @AZURA_INFO. 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 10 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 29 August 2026 โ this entry's latest reading, not the date you are reading this.
โ๐ผ๐๐๐๐ผ ๐ฝ๐๐โ (@AZURA_INFO), 78 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/AZURA_INFO.
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.