Channel
@abdugaforovIT
On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Citations Β· Cite this entry
83subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1003219109377 |
|---|---|
| Type | Channel |
| Username | @abdugaforovIT |
| Description | Informatikani biz bilan o'rganing!π @abdugaforovIT Admin: @maj_2010 |
| Created | Between 1 October 2025 and 31 January 2026β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/abdugaforovIT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 18:00 | 83 | no change |
| 9 Aug 2026, 13:00 | 83 | first reading |
20 posts held, back to 18 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 1 pageof Telegramβs post history, 20 posts per page.
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. It is computed over the 1 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days Β· latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (18 July 2026 β 9 August 2026) |
| Views total | 279 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface β not measured, not estimated |
| Readings taken | 9 Aug 2026, 18:00 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.
Lifetime counters from Telegramβs own channel header, read 9 August 2026 β not the date at the top of this page, which is when the subscriber count was last read. Below Telegramβs rounding threshold, so these counts are exact.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 1 | 100.0% |
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 1 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 1reactions 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 18 July 2026 to 9 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.
π 178-dars: Merge Conflict nima? Ba'zan ikki dasturchi bir xil kod qismiga oβzgartirish kiritadi. Git qaysi oβzgarishni saqlashni bilmay qolishi mumkin. Bunday holat Merge Conflict deyiladi. Conflict paydo boβlganda dasturchi: - ikkala oβzgarishni koβradi - kerakli kodni tanlaydi - konfliktni hal qiladi - qayta commit qiladi Bu qoβrqinchli xato emas. Jamoaviy Git ishlashda bu holat tez-tez uchrab turadi. π Xuloβ¦
π 177-dars: Code Review nima? Code Review β dasturchi yozgan kodni boshqa dasturchilar tomonidan tekshirish jarayoni. Code Review orqali: - xatolar topiladi - kod sifati oshadi - xavfsizlik tekshiriladi - yaxshiroq yechimlar taklif qilinadi Bu jarayon dasturchining bilimini oshirishga ham yordam beradi. Yaxshi dasturchi faqat kod yozmaydi, balki boshqa dasturchilar kodini ham tahlil qila oladi. π Xulosa: Code Rβ¦
π 176-dars: Pull Request nima? Pull Request β dasturchining oβz kodidagi oβzgarishlarni asosiy loyihaga qoβshishni soβrash jarayoni. Masalan, siz yangi branch da yangi funksiya yaratdingiz. Ish tugagach, uni main branch ga qoβshish uchun Pull Request ochasiz. Jamoa a'zolari: - kodni koβrib chiqadi - xatolarni topadi - fikr bildiradi - tasdiqlaydi Shundan keyin kod asosiy loyihaga qoβshiladi. π Xulosa: Pull Requβ¦
Channel photo updated
π 175-dars: Git Push nima? Git Push β lokal kompyuteringizdagi oβzgarishlarni GitHub repository ga yuborish jarayoni. Odatda jarayon quyidagicha boβladi: 1οΈβ£ Kodga oβzgartirish kiritiladi 2οΈβ£Oβzgarish commit qilinadi 3οΈβ£ GitHub ga push qilinadi Shundan keyin boshqa jamoa a'zolari siz yuborgan kodni koβrishi mumkin. π Xulosa: Git Push β lokal koddagi oβzgarishlarni remote repository ga yuborish uchun ishlatiladi.β¦
π 174-dars: Git Pull nima? Git Pull β remote repository dagi eng yangi oβzgarishlarni kompyuteringizga olib keladi. Masalan, jamoangizdagi boshqa dasturchi kodga oβzgartirish kiritdi. Siz esa shu yangilanishlarni olish uchun pull qilasiz. Bu jamoaviy ishlashda juda muhim. π Xulosa: Git Pull β remote repository dagi yangi oβzgarishlarni lokal loyihaga yuklab olish jarayonidir. @abdugaforovIT
π² Wi-Fi Haqida Wi-Fi tarmog'i uy va ofis muhitlarida internetga simsiz ulanishni ta'minlaydi. Wi-Fi, "Wireless Fidelity" so'zining qisqartmasi bo'lib, simsiz aloqa standartlariga asoslangan. Bu texnologiya yordamida bir necha qurilma bir vaqtning o'zida bitta ulanish nuqtasiga, ya'ni routerga ulanib, internetdan foydalana oladi. Hozirgi paytda yangi Wi-Fi 6 standarti yuqori tezlik va barqaror ulanishni ta'minlaydi. β¦
β€1
π 173-dars: Git Clone nima? Git Clone β GitHub dagi loyihani kompyuteringizga yuklab olish jarayoni. Bu usul orqali boshqa dasturchining yoki oβzingizning repository ingizdagi loyihani lokal kompyuterda ishlatishingiz mumkin. Clone qilingandan soβng: - kodni koβrish - oβzgartirish - test qilish - yangi funksiyalar qoβshish mumkin boβladi. π Xulosa: Git Clone β remote repository ni kompyuteringizga nusxa qilib oβ¦
π 172-dars: README.md nima? README.md β loyiha haqida ma'lumot beruvchi fayl. Yaxshi README ichida odatda: - loyiha nomi - loyiha haqida ma'lumot - ishlatilgan texnologiyalar - oβrnatish yoβriqnomasi - foydalanish usuli - loyiha rasmi yoki demo havolasi boβladi. Agar GitHub repository ga kirgan odam loyihangizni tez tushunsa, bu professional yondashuv hisoblanadi. π Xulosa: README.md β loyihangizni boshqalarga β¦
π 171-dars: GitHub bilan professional ishlash GitHub faqat kod saqlash joyi emas. U dasturchining portfolio, jamoaviy ish va loyiha boshqaruvi platformasi sifatida ham ishlatiladi. Professional loyiha uchun quyidagilar muhim: - tushunarli repository nomi - tartibli fayl tuzilishi - aniq commit xabarlari - yaxshi README fayli - muntazam yangilanib turadigan loyiha README orqali boshqa odamlar loyihangiz nima haqidβ¦
π 170-dars: Dasturchining eng muhim odatlari Kuchli dasturchi boβlish faqat kod yozish bilan cheklanmaydi. Quyidagi odatlar sizni rivojlantiradi: - har kuni amaliyot qilish - hujjatlarni (documentation) oβqish - xatolardan qoβrqmaslik - yangi texnologiyalarni oβrganish - yozgan kodni doimo yaxshilash Dasturlashda muvaffaqiyat bir kunda kelmaydi. Muntazam oβrganish va amaliyot sizni professional darajaga olib chiqβ¦
π‘Bilasizmi? Dasturiy ta'minot β bu kompyuter yoki boshqa qurilmalar uchun yozilgan dasturlar yig'indisi. Har qanday dasturiy ta'minot foydalanuvchilarga qulaylik yaratish uchun ishlab chiqiladi. Uni turli tuman maqsadlarda, masalan, ma'lumotlarni tahlil qilish, grafika yaratish yoki o'yinlar oynash uchun foydalanish mumkin. Dasturiy ta'minot doimiy rivojlanishda bo'lib, har yili bir qancha yangi funktsiyalar qo'shilβ¦
Showing the 12 most recent of 20 posts we hold for @abdugaforovIT. 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.
Citation-graph rank β 826,821 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below β republished posts weigh more than named mentions β and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channelβs name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page β a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel β 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 August 2026 β this entry's latest reading, not the date you are reading this.
βπππππβππ ππππ | πππ ππππππππ ππππππππππβ (@abdugaforovIT), 83 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/abdugaforovIT.
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.