Telegram RegisterThe public register of Telegram
Telegram profile photo for Mironshoh Inomjonov

Channel

Mironshoh Inomjonov

@mironshohinomjonov

On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

279subscribers

-5 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1001677867811
TypeChannel
Username@mironshohinomjonov
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live3 November 2026
Measurements held5
Confirmed unchanged2 times, most recently 3 November 2026
On Telegramt.me/mironshohinomjonov

Topic

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

279284281.53 September 2026 — 284 subscribers3 September 2026 — 284 subscribers12 September 2026 — 282 subscribers11 October 2026 — 281 subscribers26 October 2026 — 279 subscribers3 September 202626 October 2026
5 measurements spanning 53 days, net -5. 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 278–285 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Oct 2026, 07:36279-2
11 Oct 2026, 21:38281-1
12 Sept 2026, 02:42282-2
3 Sept 2026, 17:22284no change
3 Sept 2026, 16:47284first reading

Engagement

18 posts held, back to 25 May 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 18 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

28 Aug 2026, 05:11 UTC129 viewsread 3 September 2026
Forwarded from @muhammadsaid_dev

Tilmoch o‘yinlarini bunaqa odamlarga yoqib ketishini kutmagandim. Ommaga chiqqanida o‘sha kuniyoq 3000 ta foydalanuvchi, hozir esa kuniga 700-800 ta foydalanuvchi bu jumboqlarni yechib kelyapti. O‘zi buni menga Mironshoh taklif qildi, bir ko‘rib rostdanam bunday turdagi o‘yinlar hali qilinmaganiga amin bo‘ldim. Aksariyat shunday o‘yinlar juda sodda yoki o‘zbek tiliga mos emasdek tuyuldi. Balki kelgusida krossvordla…

20 Aug 2026, 03:41 UTC475 viewsread 3 September 2026
Forwarded from @muhammadsaid_dev

Tilmochga so‘z jumboqlarini qo‘shgandim, bir o‘ynab ko‘ringlar-chi: So‘ztop №18 4/6 ⬜️🟨🟨⬜️⬜️ 🟨⬜️⬜️⬜️⬜️ ⬜️🟨⬜️⬜️🟩 🟩🟩🟩🟩🟩 tilmoch.ai/games

19 Aug 2026, 13:08 UTC426 viewsread 3 September 2026

torch.compile() haqida yaxshi yozilgan ekan: https://depyf.readthedocs.io/en/latest/walk_through.html

24 Jul 2026, 08:30 UTC626 viewsread 3 September 2026
Forwarded from @ozodbek_pmf

Qisqa tanaffusdan keyin postlarni davom ettirmoqchiman endi. Bugun alifbodagi o'zgarishlarning texnik qiyinchiliklari va oqibatlari haqida. Dasturlar, katta til modellari va databazalardan ozroq xabari bor odam sifatida, bu tredni yozishni joiz topdim. Kelinglar alifbodagi oʻzgarishlarning kelajakdagi taʼsirini texnologiyalar qanday ishlashi nuqtai nazaridan koʻrib chiqamiz. 1. Katta til modellari. Hozirgi zamonav…

15 Jul 2026, 15:55 UTC497 viewsread 3 September 2026
Photo

Maybe it is right to bet on JEPA rather than traditional LLMs.

13 Jul 2026, 08:18 UTC476 viewsread 3 September 2026
Forwarded from @korinmas_qol

Bugun juda qiziq bir iqtibosga ko’zim tushdi va uni shu yerda qoldirgim keldi: “Uzoq vaqt menga hayot hademay boshlanadigandek tuyulardi - chinakam hayot. Biroq yo’limda hamisha bir to’siq turardi: avval yengib o’tishim kerak bir narsa, chala qolgan bir ish, hali o’tashim lozim bir muddat, uzishim kerak bir qarz. Mana shulardan keyin hayotim boshlanardi, go’yo. Nihoyat anglab yetdim: aslida shu to’siqlarning o’zi - …

8 Jul 2026, 19:15 UTC549 viewsread 3 September 2026
Forwarded from @kilich_bek_blogPhoto

🇺🇿 Yangi özbek alifbosi LLM'lar uchun ~14% «arzonroq» bo'lishi mumkin ... sababi bitta harfda Yangi xabarlarga ko'ra o'zbek tili alifbosiga o'zgartirishlar kiritilsh arafasida, asosan o'zgarishlar 4 ta harf bilan : sh→ş, ch→ç, oʻ→ö, gʻ→ğ. Tepadagi komentlarni o'qir ekanman, bizning oramizda muzokaralar boshlanda buning salbiy va ijobiy ta'sirlari haqida. Bitta qiziq bor u yerda: "balk AI uchun token tejash maqsadida…

26 Jun 2026, 13:06 UTC589 viewsread 3 September 2026
Photo

Ancha avval professor lab'iga accept qilgandiyu ana endi bugun rasman. THE (Times Higher Education) reytingida #87-o'rinda turadigan Sungkyunkwan Universitetidan MSc+PhD uchun acceptance oldim. 100% scholarship

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Talim
@Talimyangiliklari_uz · 8
Telegram ranks this channel #53 of 80 here — alongside 79 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Mironshoh Inomjonov” (@mironshohinomjonov), 279 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/mironshohinomjonov.

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.