Telegram RegisterThe public register of Telegram

Channel

🌷 ONALAR 🌷

@onalar

On this record: Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

779subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001405858878
TypeChannel
Username@onalar
Created11 November 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 6 August 2026
On Telegramt.me/onalar

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 4 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

779786782.56 Aug 2026, 09:43 — 786 subscribers6 Aug 2026, 15:34 — 786 subscribers6 Aug 2026, 23:40 — 779 subscribers6 Aug 2026, 09:436 Aug 2026, 23:40
3 measurements taken within a single day, net -7. 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 778–787 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 23:40779-7
6 Aug 2026, 15:34786no change
6 Aug 2026, 09:43786first reading

Engagement

20 posts held, back to 9 August 2025the 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.

ERR · 30 days
14.5%
avg views ÷ 779 subscribers
Avg views / post
113
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 6 August 2026
Posts held20 (9 August 20256 August 2026)
Views total226
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 15:34 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.

Recent posts

6 Aug 2026, 07:46 UTC111 viewsread 6 August 2026
Forwarded from @NomozPhoto

#quron 📜Қиёмат куни: Одамлар бир жойга жам бўладилар. Фақат Қуръонни ёд олиб, унга амал қилган киши бундан мустасно. У фаришталар — улуғ ва итоаткор элчилар билан бирга бўлади*. Қиёмат куни: Одамлар бир-биридан қочадилар ва ҳар бир киши: «ўзим, ўзим!» (фақат ўзимни қутқарсам) дейди. Фақат Қуръонни ёд олиб, унга амал қилган киши бундан мустасно. У ота-онасига виқор тожини кийдириш учун уларни излайди*. Энг бах

6 Aug 2026, 07:46 UTC115 viewsread 6 August 2026
Forwarded from @NomozPhoto

ЖАННАТ ВОЖИБ БЎЛАДИ Абу Саид Худрий розияллоҳу анҳудан ривоят қилинади: Расулуллоҳ соллаллоҳу алайҳи васаллам: «Ким: رَضِيتُ بِاللهِ رَبًّا وَبِالإِسْلاَمِ دِينًا وَبِمُحَمَّدٍ صلى الله عليه وسلم رَسُولاً «Розийту биллаҳи роббан ва бил ислами дийнан ва бимуҳаммадин соллаллоҳу алайҳи васаллама росула», деса, унга жаннат вожиб бўлади», дедилар. Маъноси: “Аллоҳни раббим деб, Исломни диним деб, Муҳаммад алайҳиссаломн

31 Aug 2025, 18:22 UTC≈20,800 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 1- Сентабр 🍁 ДУШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:27 🕰 🌅 ҚУЁШ - 05:49 🕰 🏞 ПЕШИН - 12:28 🕰 🌇 АСР - 17:01 🕰 🌆 ШОМ - 18:58 🕰 🌃 ХУФТОН - 20:15 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-2

29 Aug 2025, 16:52 UTC≈18,100 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 30- Август 🍀 ШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:24 🕰 🌅 ҚУЁШ - 05:47 🕰 🏞 ПЕШИН - 12:28 🕰 🌇 АСР - 17:04 🕰 🌆 ШОМ - 19:04 🕰 🌃 ХУФТОН - 20:19 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-21)

28 Aug 2025, 18:10 UTC≈15,800 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 29- Август 🍀 ЖУМА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:23 🕰 🌅 ҚУЁШ - 05:46 🕰 🏞 ПЕШИН - 12:29 🕰 🌇 АСР - 17:05 🕰 🌆 ШОМ - 19:03 🕰 🌃 ХУФТОН - 20:21 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-21)

26 Aug 2025, 18:19 UTC≈14,500 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 27- Август 🍀 ЧОРШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:20 🕰 🌅 ҚУЁШ - 05:44 🕰 🏞 ПЕШИН - 12:29 🕰 🌇 АСР - 17:07 🕰 🌆 ШОМ - 19:06 🕰 🌃 ХУФТОН - 20:25 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-

25 Aug 2025, 16:28 UTC≈13,000 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 26- Август 🍀 СЕШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:19 🕰 🌅 ҚУЁШ - 05:43 🕰 🏞 ПЕШИН - 12:30 🕰 🌇 АСР - 17:08 🕰 🌆 ШОМ - 19:07 🕰 🌃 ХУФТОН - 20:27 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-2

24 Aug 2025, 16:05 UTC≈11,400 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 25- Август 🍀 ДУШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:18 🕰 🌅 ҚУЁШ - 05:42 🕰 🏞 ПЕШИН - 12:30 🕰 🌇 АСР - 17:10 🕰 🌆 ШОМ - 19:09 🕰 🌃 ХУФТОН - 20:28 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-2

23 Aug 2025, 16:35 UTC≈10,200 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 24- Август 🍀 ЯКШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:16 🕰 🌅 ҚУЁШ - 05:41 🕰 🏞 ПЕШИН - 12:30 🕰 🌇 АСР - 17:11 🕰 🌆 ШОМ - 19:11 🕰 🌃 ХУФТОН - 20:30 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-2

22 Aug 2025, 16:40 UTC≈9,470 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 23- Август 🍀 ШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:15 🕰 🌅 ҚУЁШ - 05:40 🕰 🏞 ПЕШИН - 12:30 🕰 🌇 АСР - 17:12 🕰 🌆 ШОМ - 19:12 🕰 🌃 ХУФТОН - 20:32 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-21)

21 Aug 2025, 16:15 UTC≈8,530 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 22- Август 🍀 ЖУМА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:14 🕰 🌅 ҚУЁШ - 05:39 🕰 🏞 ПЕШИН - 12:31 🕰 🌇 АСР - 17:13 🕰 🌆 ШОМ - 19:13 🕰 🌃 ХУФТОН - 20:34 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-21)

20 Aug 2025, 16:39 UTC≈7,730 viewsread 6 August 2026
Forwarded from @NamozVaq1lari

☪ 2025-йил 🗓 21- Август 🍀 ПАЙШАНБА 🌙 ( Тошкент шаҳри ) 🏙 ТОНГ - 04:12 🕰 🌅 ҚУЁШ - 05:38 🕰 🏞 ПЕШИН - 12:31 🕰 🌇 АСР - 17:14 🕰 🌆 ШОМ - 19:15 🕰 🌃 ХУФТОН - 20:36 🕰 Тошкентдан бошқа шаҳарлардаги вақтлар фарқи (дақиқа) Аввал: Чимкент (-1), Конибодом (-5), Хўжанд (-6), Қўқон (-7), Жамбул (-7), Наманган (-10), Фарғона (-10), Марғилон (-10), Андижон (-11), Ўш (-14), Жалолобод (-15), Бишкек (-21),7 Олма – ота (-

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

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.

Mentions

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

“🌷 ONALAR 🌷” (@onalar), 779 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/onalar.

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.