Telegram RegisterThe public register of Telegram
Telegram profile photo for Asaka_Ziyo

Channel

Asaka_Ziyo

@Asaka_Ziyo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

69,186subscribers

+274 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001170510827
TypeChannel
Username@Asaka_Ziyo
DescriptionШаҳобиддин домла расмий канали. 📑 10.06.2019й. - 1440.06-Шаввол.
Created10 June 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live28 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/Asaka_Ziyo

Topic

Religion — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

68,89369,31969,1066 August 2026 — 68,912 subscribers6 August 2026 — 68,912 subscribers7 August 2026 — 68,915 subscribers8 August 2026 — 68,904 subscribers8 August 2026 — 68,893 subscribers9 August 2026 — 68,931 subscribers11 August 2026 — 68,947 subscribers12 August 2026 — 68,979 subscribers13 August 2026 — 68,967 subscribers14 August 2026 — 68,981 subscribers15 August 2026 — 68,997 subscribers17 August 2026 — 69,035 subscribers18 August 2026 — 69,041 subscribers19 August 2026 — 69,039 subscribers20 August 2026 — 69,004 subscribers21 August 2026 — 69,013 subscribers22 August 2026 — 69,059 subscribers24 August 2026 — 69,030 subscribers25 August 2026 — 69,073 subscribers26 August 2026 — 69,075 subscribers27 August 2026 — 69,086 subscribers28 August 2026 — 69,093 subscribers29 August 2026 — 69,112 subscribers30 August 2026 — 69,120 subscribers31 August 2026 — 69,119 subscribers1 September 2026 — 69,114 subscribers2 September 2026 — 69,156 subscribers4 September 2026 — 69,176 subscribers6 September 2026 — 69,224 subscribers10 September 2026 — 69,253 subscribers12 September 2026 — 69,291 subscribers14 September 2026 — 69,301 subscribers15 September 2026 — 69,319 subscribers17 September 2026 — 69,316 subscribers28 September 2026 — 69,186 subscribers69,1866 August 202628 September 2026
35 measurements spanning 52 days, net +274. 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 68,829–69,383 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
28 Sept 2026, 06:5769,186-130
17 Sept 2026, 16:1869,316-3
15 Sept 2026, 17:2069,319+18
14 Sept 2026, 01:5869,301+10
12 Sept 2026, 07:1869,291+38
10 Sept 2026, 01:1969,253+29
6 Sept 2026, 17:3669,224+48
4 Sept 2026, 04:1869,176+20
2 Sept 2026, 16:4869,156+42
1 Sept 2026, 17:4369,114-5
31 Aug 2026, 16:3869,119-1
30 Aug 2026, 16:4769,120+8
29 Aug 2026, 15:3569,112+19
28 Aug 2026, 12:3469,093+7
27 Aug 2026, 15:3469,086+11
26 Aug 2026, 18:4669,075+2
25 Aug 2026, 16:5769,073+43
24 Aug 2026, 14:2869,030-29
22 Aug 2026, 20:1569,059+46
21 Aug 2026, 10:3869,013first reading

Engagement

159 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 115 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
75.3%
avg views ÷ 69,186 subscribers
Avg views / post
52,100
64 posts measured
Reaction rate
0.356%
reactions ÷ views · ER floor
Posts in window
73
of 159 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 October 2026
Posts held159 (30 July 2026 – 1 October 2026)
Views total3,334,600
Reactions total11,881
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Oct 2026, 16:20 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈3,930
Videos
≈500
Links
≈1,930

Lifetime counters from Telegram’s own channel header, read 1 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
16m 07s
Average length
1m 47s

Measured directly from 9 videos 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

25,626 reactions across 141 posts, in 12 distinct kinds. The most used accounts for 59.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤15,27259.6%
👍6,59825.7%
🥰9893.86%
😢7983.11%
👏5362.09%
💯3181.24%
🤩3161.23%
🎉2651.03%
🕊2200.859%
😍2080.812%
⚡540.211%
🏆520.203%

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 141 of the 159 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 25,626 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 159 most recent posts we hold, published 30 July 2026 to 1 October 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

1 Oct 2026, 13:44 UTC≈17,400 views132 reactionsread 1 October 2026
Photo

Photo, posted without a caption

👍64❤40😍9👏7🎉4🤩3🕊2🥰2

1 Oct 2026, 13:43 UTC≈16,600 views85 reactionsread 1 October 2026
Photo

🔴 #НАМОЗ_ВАҚТЛАРИ.👇 (Асака тумани учун )⤴️ Мелодий 2026-йил 01-октябр Ҳижрий 1448 йил 20-Рабиус соний ойи ⊱•••┈••┈•❁•⊰✿✿⊱•❁•┈••┈•••⊰ ☀️⭐️ Субх 04:55 🕋🌙 Бомдод 05:35 🕋🌙 Пешин 12:50 🕋🌙 Аср 16:15 🕋🌙 Шом 18:00 🕋🌙 Хуфтон 19:50 📖 «Албатта, намоз мўминларга вақтида фарз қилингандир». (Нисо сураси, 103-оят). ⊱•┈•••❁•⊰✿🌺✿⊱•❁••┈•⊰ 🫱🌴Яқинларингизга ҳам улашинг!📲☁️🖥 🌙✅ https://t.me/Asaka_Ziyo 𝕜𝕒𝕟𝕒𝕝𝕚𝕘𝕒 𝕠𝕓𝕦𝕟𝕒 𝕓𝕠ʻ𝕝𝕚𝕟𝕘 🌙

❤46👍30🎉3🥰3🤩2😍1

1 Oct 2026, 04:01 UTC≈25,300 views123 reactionsread 1 October 2026

Posted without readable text

❤73👍33🕊6😢4🎉3🥰3🤩1

1 Oct 2026, 02:33 UTC≈23,600 views28 reactionsread 1 October 2026
File

🗣 Шаҳобиддин домла 🎧 «#Мр3_» 🌙 @Asaka_Ziyo ➖ канали учун.

❤16👍9🥰3

30 Sept 2026, 09:01 UTC≈30,000 views108 reactionsread 1 October 2026
Video

“Fatvo.uz” сайтининг мобил иловаси ишга тушди! #ХУШХАБАР Ўзбекистон мусулмонлари идораси қошидаги Фатво маркази томонидан ишлаб чиқилган “Fatvo.uz” мобил иловаси орқали диний масалалар бўйича ишончли маълумот ва жавобларни олишингиз мумкин. 📌 Илова имкониятлари: ▫️ диний саволларга жавоб олиш; ▫️ кунлик намоз вақтларини кўриш; ▫️ фатво ва савол-жавобларни мутолаа қилиш; ▫️ диний мақолалар ҳамда фойдали китоб ва манба…

❤79👍21👏2😍2😢2🤩1🥰1

30 Sept 2026, 04:01 UTC≈29,500 views143 reactionsread 1 October 2026

Posted without readable text

❤100👍25😢10🥰3🎉2👏2😍1

29 Sept 2026, 12:56 UTC≈31,600 views198 reactionsread 1 October 2026
Photo

وَلِلَّهِ مَا فِي السَّمَاوَاتِ وَمَا فِي الْأَرْضِ لِيَجْزِيَ الَّذِينَ أَسَاءُوا بِمَا عَمِلُوا وَيَجْزِيَ الَّذِينَ أَحْسَنُوا بِالْحُسْنَىٰ Маъноси: «Осмонлардаги ва ердаги барча нарсалар Аллоҳникидир. У ёмонлик қилганларни қилмишларига яраша жазолайди ва яхшилик қилганларни гўзал мукофот билан мукофотлайди». 📖 Нажм сураси, 31-оят.

❤127👍40😢11🕊6🥰6👏4⚡2🤩2

29 Sept 2026, 06:33 UTC≈32,000 views39 reactionsread 1 October 2026
File

🗣 Шаҳобиддин домла 🎧 «#Мр3_» янги 🌙 @Asaka_Ziyo ➖ канали учун.

❤22👍10👏3🥰3🤩1

29 Sept 2026, 04:24 UTC≈34,400 views165 reactionsread 1 October 2026

Posted without readable text

❤120👍29👏3💯3🕊3😢3🤩2🥰2

28 Sept 2026, 11:35 UTC≈45,300 views300 reactionsread 1 October 2026
Photo

Photo, posted without a caption

❤159👍77🎉15🥰13👏10🕊8🏆7😍6

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

Posts edited after publishing

@Asaka_Ziyo edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
7 September 2026
Most recent edit
1 October 2026

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 5 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.

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.

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

“Asaka_Ziyo” (@Asaka_Ziyo), 69,186 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/Asaka_Ziyo.

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.