✍️Ota-Onalar va Muhabbat haqidagi she'rlar, audio ijrolar muallifi Zohid Ziyoning rasmiy kanali...
📝She'rlarimizning mualliflik huquqi himoyalangan ruxsatsiz foydalanmang !!!
Murojaat : @ZohidZiyo_bot
@ONAMGAA
Created
17 January 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Music — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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
42 measurements spanning 89 days, net -2,885. 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 7,329–11,150 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)
Subscribers
Change
4 Nov 2026, 06:00
7,770
-92
31 Oct 2026, 22:30
7,862
-134
28 Oct 2026, 15:05
7,996
-108
26 Oct 2026, 01:16
8,104
-197
22 Oct 2026, 22:48
8,301
-126
20 Oct 2026, 02:59
8,427
-108
17 Oct 2026, 07:49
8,535
-191
14 Oct 2026, 06:26
8,726
-220
10 Oct 2026, 13:58
8,946
-493
4 Oct 2026, 16:15
9,439
-677
26 Sept 2026, 13:21
10,116
-463
17 Sept 2026, 15:00
10,579
-12
15 Sept 2026, 13:17
10,591
-10
13 Sept 2026, 22:01
10,601
+7
12 Sept 2026, 02:38
10,594
-7
9 Sept 2026, 15:55
10,601
-24
6 Sept 2026, 10:20
10,625
-2
4 Sept 2026, 02:21
10,627
-3
2 Sept 2026, 19:45
10,630
-11
1 Sept 2026, 15:33
10,641
first reading
Engagement
36 posts held, back to 11 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 48 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
16.5%
avg views ÷ 7,770 subscribers
Avg views / post
1,280
3 posts measured
Reaction rate
2.52%
reactions ÷ views · ER floor
Posts in window
3
of 36 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
Window
Rolling 30 days · latest post in window 30 October 2026
Posts held
36 (11 July 2026 – 30 October 2026)
Views total
3,847
Reactions total
97
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 12:02 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
≈1,940
Videos
≈3,030
Links
≈564
Lifetime counters from Telegram’s own channel header, read 6 November 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
1m 28s
Average length
1m 28s
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
1,022 reactions across 36 posts, in 20 distinct kinds. The most used accounts for 47.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
481
47.1%
👍
124
12.1%
🔥
113
11.1%
👏
72
7.05%
❤🔥
44
4.31%
😢
31
3.03%
🥰
28
2.74%
💯
25
2.45%
💘
19
1.86%
🕊
14
1.37%
😭
12
1.17%
🤝
10
0.978%
😍
9
0.881%
😁
8
0.783%
😘
8
0.783%
🤗
8
0.783%
🤩
8
0.783%
💔
5
0.489%
🎉
2
0.196%
💋
1
0.098%
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 36 of the 36 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 1,022 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 11 July 2026 to 30 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.
Telegram Stars
Stars received
32
across the posts below
Posts paid on
13
of 36 we hold a reading for · 36%
Most on one post
7
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ONAMGAA. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 36 most recent posts we hold for this entry, published 11 July 2026 to 30 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 3 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Showing the 12 most recent of 36 posts we hold for @ONAMGAA. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts edited after publishing
@ONAMGAA edited 1 post 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
22 August 2026
Most recent edit
22 August 2026
Posts recorded as deleted after publishing
We recorded 4 posts on @ONAMGAA as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
15 August 2026
Most recent seen missing
22 August 2026
Median time before seen missing
6 days
Seen missing in the last 30 days
0
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 17 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.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channel’s posts, vacant today
Evidenced gone
2
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@ONAMGAA named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@utopia_nova named in 2 posts, 16 August 2026 – 23 August 2026 · confirmed gone 7 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@sheriyat_olami_20000 named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 4 November 2026 — this
entry's latest reading, not the date you are reading this.
“꧁O͜͡N͜͡A͜͡M͜͡G͜͡A꧂” (@ONAMGAA), 7,770 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ONAMGAA.
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.
