11/90 ✅ Day 10 da asosan SQL fundament bosqichida davom etmoqda. Sekin tezlashyapmiz ⚡️ #AI #Progress #OneMoreStepForward ✈ Abduxamidov blogi
👍5⚡4🍾3😁1

Channel
@Abduxamidov_blogi
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
4,098subscribers
-1,067 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001583063764 |
|---|---|
| Type | Channel |
| Username | @Abduxamidov_blogi |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/Abduxamidov_blogi |
Education — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 26 Sept 2026, 23:59 | 4,098 | -1,636 |
| 18 Sept 2026, 02:01 | 5,734 | -786 |
| 13 Sept 2026, 13:59 | 6,520 | -532 |
| 10 Sept 2026, 02:18 | 7,052 | +333 |
| 31 Aug 2026, 23:18 | 6,719 | -1 |
| 28 Aug 2026, 15:02 | 6,720 | +1 |
| 25 Aug 2026, 11:02 | 6,719 | +1,001 |
| 22 Aug 2026, 15:15 | 5,718 | +1 |
| 16 Aug 2026, 03:37 | 5,717 | +2 |
| 12 Aug 2026, 06:38 | 5,715 | +550 |
| 9 Aug 2026, 13:11 | 5,165 | no change |
| 9 Aug 2026, 10:16 | 5,165 | first reading |
16 posts held, back to 19 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 2 pages 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 16 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos 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.
218 reactions across 16 posts, in 19 distinct kinds. The most used accounts for 26.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 57 | 26.1% | |
| 👍 | 41 | 18.8% | |
| ⚡ | 29 | 13.3% | |
| custom 5445119478708840127 | 16 | 7.34% | |
| 👏 | 15 | 6.88% | |
| 💯 | 9 | 4.13% | |
| custom 5852871561983299073 | 7 | 3.21% | |
| custom 5273927017207700510 | 6 | 2.75% | |
| ❤ | 6 | 2.75% | |
| 🤩 | 6 | 2.75% | |
| 🏆 | 5 | 2.29% | |
| 👎 | 4 | 1.83% | |
| 🕊 | 4 | 1.83% | |
| custom 5447321796204305159 | 3 | 1.38% | |
| 🍾 | 3 | 1.38% | |
| 👌 | 3 | 1.38% | |
| 🤓 | 2 | 0.917% | |
| ❤🔥 | 1 | 0.459% | |
| 😁 | 1 | 0.459% |
Custom emoji. 4 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 16 of the 16 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 218 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 19 July 2026 to 11 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Abduxamidov_blogi. 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 16 most recent posts we hold for this entry, published 19 July 2026 to 11 August 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.
11/90 ✅ Day 10 da asosan SQL fundament bosqichida davom etmoqda. Sekin tezlashyapmiz ⚡️ #AI #Progress #OneMoreStepForward ✈ Abduxamidov blogi
👍5⚡4🍾3😁1
35 000 tashabbus loyihasi 💡 Oʻzbekiston Respublikasi mustaqilligining 35 yilligiga bagʻishlangan «35 000 tashabbus» milliy platformasi orqali oʻz tashabbusimni yoritib berdim va quyidagi sertifikatga ega bo'ldim ✔️ 👉 Tashabbusingiz bormi? #tashabbus #MustaqilOzbekistan ✈ Abduxamidov blogi
👍5custom 54451194787088401275👏3
10/90 ✅ Bugundan AI Prompt Engineeringdan tashqari SQL bo'yicha boshlang'ich bilimlarni boshladim. Qiziq narsa ekan ochig'i 😁 Kecha post joylolmaganim uchun bugun 2 ta post bo'lib qoldi... ✈ Abduxamidov blogi
🔥3💯2🤩2
9/90 ✅ 🚀 PROJECT PRIME — DAY 8 Mavzu: Forecasting & KPI Target Setting BI mutaxassisi kabi kelajakni raqamlar orqali rejalashtirish BI bo’yicha mavzular tobora qiyinlashib, mavzular kengayib boryapti. Kunlik topshiriqlardagi baholarda esa ijobiy o’sish odamni ruhlantiradi 🤓 ✈️ Abduxamidov blogi
⚡4💯3🔥3
8/90 ✅ Sun'iy intellekt bo'yicha ilk kichik sertifikat tayyor ✔️ Ushbu kurs davomida quyidagi muhim yo‘nalishlar va ko‘nikmalar bo‘yicha bilimlarimni boyitdim: 🔹 Generative AI Tools — Zamonaviy AI vositalaridan samarali foydalanish 🔹 Artificial Intelligence (AI) — Sun’iy intellektning asosiy tamoyillari 🔹 Generative AI — Generativ texnologiyalarning ishlash mexanizmi va kelajagi #AI #certificate #OneMoreStepForwar…
⚡5🔥4🏆3
7/90 ✅ Bugungi mavzu: Data-driven Prompting, ya'ni AI'ga taxminiy emas, Data bilan ishlashni o'rgatish 🧠 DAY 6 — AMALIY TOPSHIRIQ BI case (vaziyat): Bir supermarket tarmog'ida: Revenue: +5% Profit: −20% Customer count: −8% Operating costs: +18% Rahbariyat sizdan: "Profit nega kamaydi va nima qilishimiz kerak?" degan savolga javob kutmoqda. Sizning vazifangiz: Shu vaziyat uchun professional AI prompt yozing. ✈️…
⚡5👍4🔥3👏1custom 52739270172077005101
6/90 ✅ 🧠 Bugungi amaliy topshiriq. Tasavvur qiling: Siz Business Intelligence Consultant sifatida supermarket tarmog'ida ishlaysiz. Muammo: So'nggi 6 oy ichida foyda (profit) 20% ga kamaygan. Sizning vazifangiz: Professional prompt yozing. 5 kunlik Prompt Engineering darslari sifatida men 9.8/10 ball oldim. Albatta kamchiligim bor va uni ustida ishlashim kerak 🟫 ✈️ Abduxamidov blogi
👍6🔥4🤓2❤🔥1🏆1👏1
5/90 ✅ 🫥 Kichik qadamlar - katta natijalar! 💪 ✈️ Abduxamidov blogi
👏7👍3🔥3🏆1🤩1
4/90 ✅ Mavzu: AI javobini boshqarish san'ati (Context Engineering) 🔑 Bugun eslab qoladigan eng muhim fikr: AI javobining sifati ko'p hollarda modelga emas, siz bergan kontekstning sifatiga bog'liq. 🔺 3 kunlik darslarim natijasida vazifani 9.7/10 bilan tayyorlab topshirdim 🟫 ✈️ Abduxamidov blogi
👍5⚡3🔥3👎1👏1💯1custom 52739270172077005101
🔸 Rol -> Kontekst -> Vazifa -> Cheklovlar -> Natija formati Ushbu formula asosida istalgan AI ga prompt yozish orqali o'zingizga kerakli natijani olishingiz mumkin Mana bir xil vazifa uchun ikki xil prompt. 1. Formula asosidagi prompt ROL: Sen Senior Business Intelligence Consultant'san. KONTEKST: Men Business Intelligence bo'yicha yangi o'rganyapman. VAZIFA: Business Intelligence nima ekanligini oddiy tilda tus…
⚡4👍4🔥3custom 54451194787088401272👏1custom 52739270172077005101
3/90 Bugungi mavzu: AI bilan muloqot emas, AI’ni boshqarish ✅
🔥4custom 58528715619832990734👍3custom 54451194787088401272❤1
2/90 ✅ AI bo’yicha chuqurroq kirishishni boshladim. Natijasini 90 kunda bilamiz nasib bo’lsa 🤝
🔥8👌3custom 52739270172077005103custom 58528715619832990733
Showing the 12 most recent of 16 posts we hold for @Abduxamidov_blogi. 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.
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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Abduxamidov Shokirjon” (@Abduxamidov_blogi), 4,098 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/Abduxamidov_blogi.
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.