Telegram RegisterThe public register of Telegram
Telegram profile photo for Azure's blog

Channel

Azure's blog

@BlogAzot

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

41subscribers

-2 since we began measuring on 14 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003829326758
TypeChannel
Username@BlogAzot
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live30 October 2026
Measurements held6
Confirmed unchanged2 times, most recently 30 October 2026
On Telegramt.me/BlogAzot

Topic

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 29 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 the other topics.

Growth

41454314 September 2026 — 43 subscribers14 September 2026 — 43 subscribers16 September 2026 — 45 subscribers29 September 2026 — 43 subscribers9 October 2026 — 42 subscribers24 October 2026 — 41 subscribers14 September 202624 October 2026
6 measurements spanning 40 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 40–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Oct 2026, 19:4841-1
9 Oct 2026, 13:5742-1
29 Sept 2026, 07:5843-2
16 Sept 2026, 00:4045+2
14 Sept 2026, 17:2243no change
14 Sept 2026, 16:4743first reading

Engagement

20 posts held, back to 18 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 20 posts for this entry, the most recent from 14 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

18 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 38.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💊738.9%
💔527.8%
🤡316.7%
🎃15.56%
👀15.56%
🔥15.56%

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 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 18 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 18 August 2026 to 14 September 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.

Recent posts

14 Sept 2026, 17:11 UTC2 viewsread 14 September 2026
Forwarded from @twofourconf

🤩 . ( 🌟🌟 ) ♡ 🙂 ~ искал кф по ТуФоурам??? ➿➿➿➿➿➿➿ Тогда ты пришёл в правильное место! 🌟🌟 . / · ^ 🪽🪽 · 🌟🌟 Cr на фото: rorytwoo on pinterest Вп пост ; тейк бот ; навигация ⑅ ➿➿➿➿➿ .

14 Sept 2026, 17:06 UTC3 viewsread 14 September 2026
Forwarded from @forsakenstickersofficalPhoto

ᅠִ. 𝐖𝐄𝐋𝐂𝐎𝐌𝐄 ࣪𖤐⏝°⏝ ୨୧ ⏝°⏝ִ ࣪𖤐 [ 🥀 ] - Χⲟ̤̮ɥⲉ๋࣭ⲧ̤̮ⲥ๋࣭я ⲥ๋࣭ⲧυ̤̮ⲕⲉⲣ๋࣭ы ⲡ̤̮ⲟ ⲫ๋๋࣭࣭ⲟⲣ๋๋࣭࣭̤̮с̤̮у ๋࣭υ ⲟ̤̮ɥ๋࣭ⲉ๋࣭ⲏ̤̮ь ⲕ̤̮ⲣⲁⲥ๋̤̮࣭υⲃ๋࣭ы̤̮ⲉ Α̤̮ⲃ๋࣭ы... ︵᷼⏜ ๋࣭ ⭑ ︶꒷꒦︶๋࣭ ๋࣭ ⭑⸻⸻ִ ࣪𖤐 [ 🥀 ] - Χ๋࣭ⲟ̤̮ɥ๋࣭ⲩ ⳝⲁ๋࣭ⲏ̤̮ⲏ๋࣭̤̮ⲉⲣ̤̮ы ⲇ̤̮ⲗ๋࣭я ⲧ̤̮ⲃ๋࣭υ๋࣭̤̮т๋࣭̤̮ⲧ̤̮ⲉⲣ๋࣭ⲁ, ю๋࣭̤̮ⲧ๋๋࣭࣭̤̮ⲩⳝ̤̮ⲁ, Πυ๋࣭ⲏ๋࣭ⲧ̤̮̤̮ⲉⲣ๋࣭ⲉⲥ๋̤̮࣭ⲧ и д̤и̤ск๋࣭о̤̮р๋࣭д๋๋๋࣭࣭࣭̤̮а....꒱.𖥔 ݁ ˖ ࣪𖤐⏝°⏝ ୨୧ ⏝°⏝ִ ࣪𖤐 ⌣๋࣭ ⭑ⲏ̤̮ⲉ ⲥ๋࣭̤̮ⲧⲟ๋࣭̤̮υ๋࣭ⲧ ⲡ̤̮ⲉ๋࣭ⲣ̤̮ⲉ̤̮ⲿ๋࣭и̤̮ⲃⲁ๋࣭̤̮ⲧ̤̮ь, ⲃⲉ๋࣭ⲇ̤̮ь ⲧ̤…

14 Sept 2026, 17:01 UTC3 viewsread 14 September 2026
Forwarded from @twotimecffPhoto

🌟🌟🌟 🌟𝕨o͟͟🔹ⅈ𝑚ᥱ 🤩 ̶a̶̶i̶ℓ𝕪 𝒸𝘧 nонpавuлсR ̶Т̶у 𝕋айm из 𝘍o̶̶r̶̶s𝕒ƙeн? t𝕙e̶̶𝘯 . . 🌟🌟🌟🌟🌟🌟 ۟ ⏜𑩑︵ 🤩𝕖ᥣco𝘮ᥱ יִיִ 🌟🌟

13 Sept 2026, 12:02 UTC17 views2 reactionsread 14 September 2026

New message by . . . ME! Из почты. . . И так поехали 1. Шляпа имеет свой характер личность или она просто как часть тебя как собеседник? 2. Ты знаком с кем то из выживших кроме тайма? 3. Какие у вас сейчас отношения с таймом? 4. Я знаю что твои цветы ядовиты в употреблении в пищу и что у тебя неуязвимость к этому яду но все же что на счёт Джона ты давал ему чай из этих цветов? 5. У твоих цветов есть применения кром…

🤡2

13 Sept 2026, 12:01 UTC17 views1 reactionsread 14 September 2026

New message by . . . ME! „Как же все таки сллжно писать когдп ты ничкго не видншь. Даров, я, кажттся, опять пррпал? Ладно, прлехали. Я так и не поздрввил вас с 1 сентября, слвсем забыл об этом. Чтож, лцчше поздно,чем никогда, верно? Хах. Писать мне по пркжнему нечего, но, к моему счастью, впкрвые за столь долгое время мнк в пвчту пришло сообщение, этр радует.” To . . . idkwhotsperson YOU!

🤡1

10 Sept 2026, 19:42 UTC27 views1 reactionsread 14 September 2026

NEW . . . RP action!!! посмотрев на протянутый ему подарок, Азур быстро вытянул его из рук Доу, чуть ли не расцветая от радости. — ДА НУ, ЭТО МНЕ? Ещё около минуты Азур рассматривал гербарий, попутно с этим хихикая как довольный ребёнок. Наконец закрыв гербарий, Азур тут же кинулся на Доу в объятия, буквально повиснув на нём. Спустя некоторое время он всё же отцепился, отойдя на пару шагов. — Спасибо, Джон, это..…

🔥1

3 Sept 2026, 13:30 UTC52 views1 reactionsread 14 September 2026

NEW . . . RP action! Обернувшись на хрип, Азур тут же подорвался с места, на всех порах подлетев к Доу — ПРИВЕЕЕЕЕТ Голос Азура звучал так, будто они лет сто не виделись — Я уж думал ты забудешь куда– Неважно. Тааак, как у тебя делааа??? обратив внимание на сжатую лапу Доу, Азур слегка прищурился, пытаясь понять что он там прячет блять

💊1

3 Sept 2026, 11:33 UTC41 views1 reactionsread 14 September 2026

New message by . . . ME! „ну ты и заинтриговал, Доу. Пошли конечно, всё равно делать нечего, будет хоть с кем поговорить” to . . . John Doe!

👀1

3 Sept 2026, 11:10 UTC36 viewsread 14 September 2026

New message by . . . ME! „И тебе привет У меняяя всё относительно нормально, сижу отдыхаю ... В целом как и всегда. Ну, как я уже неда- Давно писал, у меня зрение ухудшилось. Да и всё, больше я ничем похвастаться к твоему сожалению не могу. На счёт времени, осень я конечно люблю, но не прям сильно, так что ... 50/50” to . . . John Doe!

29 Aug 2026, 17:28 UTC47 views7 reactionsread 14 September 2026

New message by . . . ME! „нет.” to . . . John Doe

💔5💊2

Showing the 12 most recent of 20 posts we hold for @BlogAzot. 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.

Forward network

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.

Mentions

Named by 1 registered channel — 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.

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.

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 24 October 2026 — this entry's latest reading, not the date you are reading this.

“Azure's blog” (@BlogAzot), 41 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/BlogAzot.

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.