Telegram RegisterThe public register of Telegram

Channel

[Не работает] Old-Azure

@OldAzure

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

17subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003954748597
TypeChannel
Username@OldAzure
CreatedBetween 1 April 2026 and 9 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/OldAzure

Growth

177 August 2026 — 17 subscribers11 August 2026 — 17 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 16–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:1717no change
7 Aug 2026, 19:1117first reading

Engagement

20 posts held, back to 9 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 30 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
47
Videos
3
Links
32

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
25s
Average length
25s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

12 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎650.0%
😭325.0%
216.7%
🥰18.33%

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 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 12reactions 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 9 May 2026 to 30 May 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

27 May 2026, 10:22 UTC57 views7 reactionsread 11 August 2026

@V1r7sn49_ozvuchka @DW_CONF_YPA Прошу подпишитесь на них...

👎61

27 May 2026, 10:20 UTC57 views3 reactionsread 11 August 2026

ᗩZᑌᖇE-Ребят... Это владелец...к сожалению из сетки этого канала больше нет...Так что извините но я удаляю этот канал и попрошу присоединится к моим другим каналам.

😭3

26 May 2026, 12:55 UTC54 viewsread 11 August 2026
Video

Если у тебя были мысли например: блин так мало рофло-блогов,хочу следить за одним таким или Керт такой сасный хочу о нем узнать или вы просто Андрей 신을 Ꮺ . 𝘇Zz ♡ . 𑁯ᰍ (!) . ⊹ ТО ТОГДА ВАМ К НАМ 신을 Ꮺ . 𝘇Zz ♡ . 𑁯ᰍ (!) . ⊹ Керт- рофельное божество с бинтами на глазах, он одет в пальто, футболку, штаны, брюнет, цвет глаз фиолетовый дисклеймер: последующие события в

25 May 2026, 18:15 UTC47 viewsread 11 August 2026

#вп_криттик

Signed [не отвечаю с 22:10 до 9:00]🪼 ⃝ Krittik ꕀ🌿#YH

25 May 2026, 18:15 UTC35 viewsread 11 August 2026
Photo

[НУЖДАЕМСЯ В АДМИНАХ] 💌🔞 🔤🔞🤩💌 🌟🌟🌟🌟🌟🌟🌟🌟🌟 🗝🗝🗝🗝 🗝ᥴꪚᥱᥲⲙ’ઽ ꪮᥲⲙᥱઽ🤩 🗝🗝 🌟🌟🌟 🙂 - 💌ρᥙʙᥱᴛᥴᴛʙую ᴛᥱδя, ⲙᥙᥴᴛᥱρ ᥙ᧘ᥙ ⲙᥙᥴᥴᥙᥴ! Я ᧐чᥱнь ρᥲдᥲ ᴛᥱδя ʙᥙдᥱᴛь! И я ᥰρᥙᴦ᧘ᥲɯᥲю ᴛᥱδя ʙ ᥴʙ᧐ᥔ κᥲнᥲ᧘ ᥰ᧐ ⲙᥙρу дᥱндᥙ ᥙ ᥴ᧐нᥙκу🔞 𐋏ᥲдᥱюᥴь, чᴛ᧐ ᴛᥱδᥱ ᤋдᥱᥴь ᥰ᧐нρᥲʙᥙᴛᥴя 🌟🌟🌟🌟 🌩🌩🌩🌩🌩🌩 🔤Вᥱдь ᤋдᥱᥴь ʙᥲᥴ ждᥱᴛ:: 🗝Иᴦρы ᥰ᧐ ɗᥲᥒɗy’s ᥕ᧐rᥣɗ κᥲждыᥔ дᥱнь! 🗝Аρᴛы, н᧐ʙ᧐ᥴᴛᥙ ᥙ ᥙнᴛᥱρᥱᥴныᥱ ɸᥲκᴛы ᥰ᧐ ɗᥲᥒɗy’s ᥕ᧐rᥣɗ ᥙ s᧐ᥒiᥴ! 🗝𐌗᧐ρ᧐ɯᥱᥱ ᧐ᴛ

Signed [не отвечаю с 22:10 до 9:00]🪼 ⃝ Krittik ꕀ🌿#YH

25 May 2026, 16:39 UTC70 views1 reactionsread 11 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 -Это что союз?... Союз между: @OldAzure 🌟🌟🌟 @BobettesRuns Пожелайте им счастливого брака!.. 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩

🥰1

Signed [ᗩZᑌᖇE]

25 May 2026, 16:21 UTC25 viewsread 11 August 2026
Photo

⚡️ - Я не могу найти стикеры с "... "! ⚡️ - а мне хочется найти комфортный канал со стикерами.. ⚡️ - Гав! Гав! ⚡️ - что здесь делает пебл?! 💭💭💭💭💭💭💭💭💭 ⚡️ - Ого, как много тунов, но у них одна проблема! Что ж, я представляю вам канал по миру денди, где вы можете найти себе подходящии стикеры! ⚡️ - *тап* Здесь круто И здесь Тут тоже

Signed [ᗩZᑌᖇE]

25 May 2026, 16:07 UTC27 views1 reactionsread 11 August 2026
Forwarded from @pizzadeptcf

🤩︶⏝ 🔠ᴇʟᴄᴏᴍᴇ to..⚡ 🌚 🤩 🤩IŻZÅ🤩ĒPT ко́нф 📎 🪽🌟🤩🤩🤩🌟🪽 ✨ :▸ 🌟🌟⚡ ᥬᥒᥲ᥎іgᥲ𝗍і᥆ᥒ ░⚡ Ɜдᴇᴄь ʙы уʙидиᴛᴇ ᴇжᴇднᴇʙный ᴋᴏнᴛᴇнᴛ ᴨᴏ дᴀннᴏʍу ɯиᴨу‼️

1

Signed [ᗩZᑌᖇE]

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

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

“[Не работает] Old-Azure” (@OldAzure), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/OldAzure.

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.