Channel
@Mahalla_Fuqarolar_Yigini
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,152subscribers
-90 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001793873117 |
|---|---|
| Type | Channel |
| Username | @Mahalla_Fuqarolar_Yigini |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Mahalla_Fuqarolar_Yigini |
Sports — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 00:58 | 3,152 | -31 |
| 12 Sept 2026, 17:00 | 3,183 | -7 |
| 8 Sept 2026, 12:37 | 3,190 | -15 |
| 2 Sept 2026, 20:42 | 3,205 | -10 |
| 31 Aug 2026, 05:04 | 3,215 | -9 |
| 28 Aug 2026, 04:13 | 3,224 | -14 |
| 24 Aug 2026, 18:54 | 3,238 | +26 |
| 20 Aug 2026, 17:36 | 3,212 | -16 |
| 17 Aug 2026, 18:24 | 3,228 | -3 |
| 14 Aug 2026, 16:48 | 3,231 | -21 |
| 11 Aug 2026, 10:54 | 3,252 | +12 |
| 8 Aug 2026, 16:08 | 3,240 | -2 |
| 8 Aug 2026, 10:46 | 3,242 | first reading |
20 posts held, back to 7 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
717 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 46.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 336 | 46.9% | |
| 👍 | 200 | 27.9% | |
| ❤ | 92 | 12.8% | |
| 👎 | 54 | 7.53% | |
| 🤔 | 22 | 3.07% | |
| 🤯 | 5 | 0.697% | |
| custom 5228818294252801479 | 4 | 0.558% | |
| custom 5226780637213531303 | 2 | 0.279% | |
| 🔥 | 2 | 0.279% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 20 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 717 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 7 August 2026 to 8 August 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.
Arauxoni plyuslari ko'p, lekin bekorga Barselona uni qo'yib yubormayapti. Iraola ham shu Flik kabi himoyani yuqori linyaga qo'yadi. Arauxo bu sistemada juda kuchli emas. Keyin Iraola himoyachilari to'p bilan juda qulay ishlashi kerak (Huysen bilan Zabarni misol), Arauxo bunga ham to'g'ri kelmaydi. Bizga plyus tarafi, bu ijaraning risklari kam. 1 yil o’ynaydi, yaxshi o’ynab ketsa, sotib olishimiz mumkin. Yaxshi o’yn…
👍13
Signed AJ
Aslida bunaqa yurishlar menga yoqiyapti, imi jimida Munyos va Arauxoni oldik, arzon va budgetni narxlarga. Shu Barkoylani olmasdan boshqa no name o’yinchi olsa ajablanmayman umuman. Iraola ancha ayyor chiqti…👌
❤21👍2
Signed Hojimurod Muzaffarov
Yo’q sizlar nimaga Arauxoni past baholayapsizlar mensimayapsizlar? Shunchaki Flikni offiside timizmiga tushulmagani uchunmi? Aslida bizga shunaqa Destroyer o’yinchi kerak emas edimi? Yo’qdan ko’ra bori yaxshi emasmi? Aytgancha u o’ng tarafdaham bemalol o’ynaydi.
👍22❤6custom 52288182942528014794🔥1
Signed Hojimurod Muzaffarov
Video, posted without a caption
🤣32👍1👎1
Signed Hojimurod Muzaffarov
Menimcha, transfer qilmaganimiz sababi, Iraolaga umuman ishonch yo'q. Hozir u xohlagan futbolchilarni olib kelganimiz bilan, keyingi mavsum Slot qaytgach, Iraola olib kelgan futbolchilarni yo'qotishga to'g'ri kelib qolishi mumkin.
🤣50👎1
Signed Sardor Ollamberganov
Bu yoz markaziy himoyachi transfer qilmaganimizni asosiy sabablaridan biri menimcha keyingi yoz Jarell Kuansani qaytaramiz. Keyingi yoz uni 52 mln funt evaziga qayta sotib olishga haqqimiz bor. Kuansa yanayam o’sishga erishsin bu mavsum, zo’r himoyachi bo’lish uchun hamma narsasi yetarli
👍25❤7
Signed AJ
Tobi Alderveyreld "Tottenxem"ning Kodi Gakpoga bo'lgan qiziqishi haqida: «Nima uchun "Liverpul" Kodi Gakponi "Tottenxem"ga sotishi kerakligiga tushunmayapman, axir u har qanday jamoa uchun asosiy tarkib o'yinchisi. U yirik gavdali, ammo shu bilan birga juda tezkor, chapda ham, o'ngda ham o'ynay oladi — markazga ko'chib, to'g'ri darvoza tomon yuradi. Unga qaraganimda, hatto to'p maydonning boshqa chetida bo'lsa ham,…
🤣29❤5👍1
Signed Sardor Ollamberganov
Bu transfer 3 yil oldin bo’lganda, Liverpul muxlislaridan xursandi bo’lmasdi. Afsuski Arauxo 3 yil ichida juda ko’p jarohatlar oldi va juda ko’p “qovunlar” tushirdi. Shunday bo’lsa-da, endigina 27 yosh. Nima ham derdik, omad tilaymiz, yaxshi va jarohatsiz mavsum o’tkazsin. Jo Gomez 2.0 muborak hammamizga
👎28🤣19❤2
Signed AJ
Barsachilar xursand hammasi Arauxo ketganiga
🤣46❤2👎1
Signed Alisher
Agar Arauxo yorib yuborsa sotib olsakham bo’lar ekan…)
❤29
Signed Hojimurod Muzaffarov
Arauxo yoradi hali.
👍27👎11🤔5❤1
Signed Hojimurod Muzaffarov
Arauxooo
👎12👍6🤯5
Signed Hojimurod Muzaffarov
Showing the 12 most recent of 20 posts we hold for @Mahalla_Fuqarolar_Yigini. 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.
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.
Named by 2 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Mahalla Fuqarolar Yig'ini” (@Mahalla_Fuqarolar_Yigini), 3,152 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Mahalla_Fuqarolar_Yigini.
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.