Channel
@azure1xcf
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
513subscribers
+55 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003750205598 |
|---|---|
| Type | Channel |
| Username | @azure1xcf |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/azure1xcf |
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 15 Sept 2026, 08:15 | 513 | -5 |
| 8 Sept 2026, 00:17 | 518 | +3 |
| 29 Aug 2026, 16:54 | 515 | +1 |
| 23 Aug 2026, 09:09 | 514 | +7 |
| 15 Aug 2026, 19:17 | 507 | +49 |
| 8 Aug 2026, 04:50 | 458 | no change |
| 7 Aug 2026, 15:46 | 458 | first reading |
15 posts held, back to 4 August 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 15 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
56 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 44.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5453895844946281736 | 25 | 44.6% | |
| custom 5246984335172591971 | 16 | 28.6% | |
| ❤ | 9 | 16.1% | |
| custom 5406614993821010571 | 3 | 5.36% | |
| 💋 | 2 | 3.57% | |
| ❤🔥 | 1 | 1.79% |
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 10 of the 15 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 4 August 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.
🔤авно хотел посмотреть за своим любимым пейрингом, но негде? Тогда ты по адресу! Welcome to... 🍁➖➖➖➖➖ ➖➖➖➖➖➖🍁 ➖➖➖➖➖➖➖ ➖➖ ➖➖➖➖➖ Пре-форсакен Пре-кулкид ау 🖤🖤🖤🖤🖤🖤🖤🖤🖤🍁 Рт пост Вп пост Буст Анон Севена Анон Эллиота Правила 🤍: База, хейт пиццабургеры
Signed schwärch
☺️юбишь такой пейринг, как ноли7н7...?🌟🌟 ☺️щешь по нему контента? 🌟 🤩🤩 Или тебе просто интересно посмотреть на чужое творчество? 💜 🌟🌟🌟🌟Тогда тебе нужно в... 🌟🌟🤯🤯🤯🤯🤯🤯 🌟🌟🤯🤯🤯🤯🤯🤯 🌟🌟🤯🤯🤯🤯🤯🤯 🌟🌟🤯🤯🤯🤯🤯🤯 🌟🌟🤯🤯🤯🤯🤯🤯 🌟🌟🤯🤯🤯🤯🤯🤯 ❌🤯🤯🤯🤯🤯🤯 😀🌟☺️менно здесь каждый день выкладывается контент ПО ЛЮБЫМ 7н7ноли!! 🌟🌟☺️ейк бот для творческих - @Svinolitakesbot 😀🌟☺️авигация для самых любознательных🌟
Signed schwärch
[Знакомые ситуации??:] ♥️:Я нарисовал(-а) арт по Спеллиот, но не знаю с кем можно поделиться им :( ♥️:по Эллиот × Спектр так мало контента, где можно найти ещё :( ♥️:что такое Спеллиот— [У нас есть решение!!] Добро пожаловать в Spelliot confession Spelliot — это пейринг между персонажами Forsaken, а именно Эллиот × Спектр Мы знаем, что Эллиот оригинально является персонажем из плейса Work at a pizza place, однако …
Signed schwärch
📝🍌:: был переезд,проверьте подписку🤩🌟 🤩 🌟 :: 🔤hat?? 🤩 🍼🍼 🔤чередной орно кф по форсакену снесли... И теперь тебе негде потеребонькать на любимые пиксели, не выходя из 🔤g?? 🌟🌟 🌟🌟 [16+] NSFW FORS ⌗CONF 🤩 🤩 cr: @pisslovwr69 🤩 🤩 переходник *тап 🤩 вп пост *тап 🤩 😋
Signed schwärch
• 𝑇𝐴𝐾𝐸 • 🍫 Давненько меня не было, в последнее время особо желания рисовать не было, но я закончил концепт с дизайном 1х4 и Тимурчика. Что бы облегчить себе представление о них и что бы вы посмотрели ТГК: @chocolate_0481 @azure1xcf @Doublezippertake_bot #тейк
custom 54538958449462817369❤2custom 52469843351725919711
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • Тгк: @c1ntes [18+] @azure1xcf @Doublezippertake_bot #тейк
custom 54538958449462817363❤🔥1custom 54066149938210105711
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • @azure1xcf @Doublezippertake_bot #тейк
custom 54066149938210105712custom 54538958449462817362
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • 😭✌️🥀 Если что он на азура наяривает 😔 Тгк: @c1ntes [18+] @azure1xcf @Doublezippertake_bot #тейк
custom 54538958449462817363
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • 😭✌️🥀 Тгк: @c1ntes [18+] @azure1xcf @Doublezippertake_bot #тейк
custom 54538958449462817363
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • Можно я вам тут не моих артов накидаю?? Хе-хе Cr: @ecstxsyz (тт) @azure1xcf @Doublezippertake_bot #тейк
custom 52469843351725919714
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • 🍫 Ночной скетч из роблокса с тем самым мемом.. Чёрные.. ТГК: @chocolate_0481 @azure1xcf @Doublezippertake_bot #тейк
custom 52469843351725919713
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
• 𝑇𝐴𝐾𝐸 • Хэдканоны на Даблширинки: 1) 1х1х1х1 заинтересовался в Азуре первым так как после попадания в форсакен Азур пытался помогать всем, а 1х1х1х1 для личного самоутверждения хотел найти в нем корыстные цели. По итогу 1х1х1х1 просто ходил за Азуром по пятам и второго это немного напрягало 2) по итогу 1х1х1х1 начал пропитываться эмпатией и пониманием к Азуру (особенно когда тот рассказал про Ту Тайма и культ), …
custom 52469843351725919716custom 54538958449462817364
Signed 𝔊𝔩𝔦𝔱𝔷 🩻
Showing the 12 most recent of 15 posts we hold for @azure1xcf. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐷𝑜𝑢𝑏𝑙𝑒𝑧𝑖𝑝𝑝𝑒𝑟 𝐶𝑜𝑛𝑓𝑒𝑠𝑠𝑖𝑜𝑛 / 𝑑𝑎𝑖𝑙𝑦” (@azure1xcf), 513 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/azure1xcf.
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.