Channel
@mukhammadjon_tech
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
64subscribers
+0 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001905844337 |
|---|---|
| Type | Channel |
| Username | @mukhammadjon_tech |
| Created | Between 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/mukhammadjon_tech |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 05:40 | 64 | +1 |
| 31 Aug 2026, 02:36 | 63 | -1 |
| 16 Aug 2026, 15:34 | 64 | no change |
| 15 Aug 2026, 02:32 | 64 | first reading |
20 posts held, back to 15 December 2024 — 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 1 January 2026. An engagement rate over an empty window would be a number about nothing.
89 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 47.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 42 | 47.2% | |
| ❤ | 14 | 15.7% | |
| 👍 | 10 | 11.2% | |
| ⚡ | 7 | 7.87% | |
| 👏 | 7 | 7.87% | |
| 😁 | 7 | 7.87% | |
| ✍ | 1 | 1.12% | |
| 🕊 | 1 | 1.12% |
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 89 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 15 December 2024 to 1 January 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mukhammadjon_tech. 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 20 most recent posts we hold for this entry, published 15 December 2024 to 1 January 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.
Biror loyiha ustida ishlayapsiz Asosiy koʻrsatgichingiz nima? Obunachi? Mijozlar soni? Hech qaysisi emas Bizda negadir obunachisi koʻp boʻlsa, yaxshi shakllangan deb oʻylaymiz Aslida qanday? Aslida algoritmlarni aldash mumkin, oxvat, obunachi keladi, lekin maqsadli emas Bu holatda siz fokus qaratishingiz zarur boʻlgan narsa baza 🔥 Baza qancha katta boʻlsa shuncha koʻp sotuv qilish mumkin Bir reklamadan 1000 …
⚡1👏1
4 yil oldin, sovuq qish paytida ikki talaba bir xil vakansiyaga ishga topshiradi Bu talabalarning ikkisi qabul qilinadi, kursdoshlaridan aqlliroq, ko'proq o'qiydigan, lekin bir biriga juda o'xshaydi Yaqinda, bitiruv bo'lib o'tdi 5 yillik yig'ilish Hali ham ular bir-biriga juda o'xshash, ikkisi baxtli turmush qurishgan, ishlaridan mamnun Biri yaxshi kompaniyada yaxshi lavozimda Ikkinchisi esa allaqachon shu sohad…
⚡1🔥1
Qo'rquvni faqat undan ham kuchliroq bo'lgan qo'rquv bilan yengib bo'ladi. Ko'p vaziyatlarda qiyin qarorlarni qabul qilishga qo'rqamiz. Siz bilan ishdagi, biznesdagi qo'rquvlarni ko'rib chiqamiz. Masalan: Sizda Potensial mijozni raqami bor, telefon qilib sotishga qo'rqasiz. Telefon qilishdan oldin har hil hayollar keladi. Shu holatda siz xis qilayotgan bitta qo'rquv bo'r — shu mijozga sota olmaslik, shu mijoz bilan…
❤2🔥2⚡1👍1
Digital sohada xizmatni sotish uchun, o'sha xizmatni o'zingiz qila olishingiz shart emas. Sayt sotish uchun, sayt yasashni bilish shart emas. Buning uchun siz sotayotgan xizmatingizni juda chuqur tushunishingiz kerak. So'ng xizmat ko'rsatish uchun kerak bo'ladigan barcha bosqichlarni bilishingiz kerak. Sotish uchun nimalarni bilish kerak? Keling web-sayt misolida ko'rib chiqamiz: Muammo: 1. Kim uchun bu xizmat ker…
👍2🔥2⚡1😁1
Birodarlar, do'stlar ish ko'p, loyihalar ko'p. Yaxshi mijozlar ko'p. Telefonni o'chirish, har kuni bir joyda o'tirib deep work qilish, sohangizda TOP mutaxassis bo'lish kerak bo'ldi. Man tushunmayman mijoz yo'q, pul yo'q deb yurgan odamlarni. Shularni hammasida quyidagi muammo bor: 1. Ishini ustasi emas, yoki chala ishlaydi yoki sifatsiz yoki sekin ishlaydi. 2. Qo'lidan ko'p narsa kelmaydi lekin xizmatini narxi …
🔥3👍2😁1
Effortless kitobidan 15 ta instrument 1. Invert — har qanday qiyin vazifa oldingizda turgan bo'lsa, bir marta bo'lsa ham savol berib ko'ring — oson yo'li bo'lsachi? Mutlaqo teskari usul bo'lsachi? Masalan 10.000$ daromad bir oylik maqsad bo'lsa 1000$ dan 10 ta odamga xizmat ko'rsatish mumkin, balkim 1 ta 10.000$ ga sotish mumkindir? Yoki sotmasdan pul ishlash mumkindir? 2. Enjoy — ishlarni nima qilsangiz qiyinchil…
🔥3❤1
Uyda ishlash, ofisda ishlash juda qiyin bo'lar edi. Lekin nima uchundir kafeda yoki Impactda ishlasam samarali ishlayman, ishlash juda yoqadi. Sababini tushunmas edim. Hozir topdim )) Bu devorga qarab ishlaganim uchun ekan. Yani ish stoli devorga qaratilgan bo'lsa bu charchoqni, siqilishni keltirib chiqarar ekan. Eng qizig'i bu bo'yicha tadqiqotlar ham bor ekan. Ofisda ham, uyda ham ish stoli devorga qaratilgan. H…
😁5🔥2⚡1❤1
Kompyuter klaviaturasida istalgan tugmani bosish ehtimoli 1/104, ya’ni 0.009 ga teng (104 talik standard klaviaturani hisobga olsak). Juda kichkina raqam. Ammo o‘sha tugmani bosmaslik ehtimoli 0.99 ga teng. Birinchisidan qariyb yuz barobar katta. Hayot ham shunday: xato qilish ehtimoli bor, lekin xato qilmaslik imkoniyati undan yuzlab marta kattaroq bo'ladi. Shunchaki bir marta sabr qilish, bir marta Enter tugmasini…
🔥3
Freelanser pozitsiyasidan → tadbirkor pozitsiyasiga o'tish uchun 1 ta eng katta va eng qiyin qadam. Siz bilan freelanser va tadbirkor fikrlashidagi farqlarni ko'rib chiqamiz. Fikrlash 2 xil bo'lar ekan: 1. Ketma-ket fikrlash (Линейное мышление) — odam bajarishi kerak bo'lgan ishlarni ko'rganida birinchi navbatda miyyasida bu ishlarni qilishga qancha vaqt ketishi, qancha kuch ketishi, qaysi ketma-ketlikda bajarish…
🔥3✍1🕊1
2019 2020 2021 2022 2023 2024 Yillarda butun fokusim daromadni oshirish va shunga yordam beradigan bilimlarni olishga qaratilgan edi. Endi tushunib yetyapman, daromadni oshirishga yordam beradigan instrumentlarni bir necha oyda organib olish mumkin ekan, lekin ularni amalga oshirishga kerak bo'ladigan fikrlash, intizom va tizimni esa qurish uchun yillar kerak ekan. Hozir ham kech emas, lekin imkonim bo'lganida bu …
🔥6👏2⚡1
Odam umri davomida 7 ta (richag, leverage) larni rivojlantirishi kerak ekan. 1. "Specific" bilim — bu maktabda, yoki treninglarda o'rganib bo'lmaydigan, faqat sizga xos bilim. Bu bilim / ko'nikmani siz o'yindek qabul qilasiz, lekin boshqalar uchun bu o'g'ir mexnatdek tuyuladi. Masalan man uchun yozish / o'qish / dars berish / rejalashtirish juda oson, soatlar qilishim mumkin, boshqalar uchun juda zerikarli ish. Ayn…
🔥3❤1
Mijozdan to'g'ri TZ olish uchun sarflangan har bir daqiqa, ish boshlangandan keyin sizga bir necha soat vaqt tejab beradi. TZ'ni to'g'ri shakllantirish uchun ayalgan har bir daqiqa, bir necha soat, balki kun vaqt yoqotilishiga olib keladi! Dizayner va dasturchilar uchun. TZ (Техническое задание) texnik vazifa — loyiha qanday ko'rinishda bo'lishi, ranglar, ketma-ketlik, ma'lumotlar, referenslar, loyihaning funksiona…
🔥3
Showing the 12 most recent of 20 posts we hold for @mukhammadjon_tech. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Mukhammadjon Muminov | Tech” (@mukhammadjon_tech), 64 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mukhammadjon_tech.
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.