Telegram RegisterThe public register of Telegram
Telegram profile photo for Bekzod G‘ayratov

Channel

Bekzod G‘ayratov

@bekzod_gayratov

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

70subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001223724555
TypeChannel
Username@bekzod_gayratov
Created15 April 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live13 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 13 September 2026
On Telegramt.me/bekzod_gayratov

Growth

707371.57 August 2026 — 73 subscribers9 August 2026 — 73 subscribers21 August 2026 — 72 subscribers27 August 2026 — 70 subscribers7 August 202627 August 2026
4 measurements spanning 20 days, net -3. 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 70–73 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 15:5370-2
21 Aug 2026, 09:0572-1
9 Aug 2026, 22:3273no change
7 Aug 2026, 19:4773first reading

Engagement

20 posts held, back to 24 March 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 6 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 12s
Average length
2m 12s

Measured directly from 1 video 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.

Reaction mix

91 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 51.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4751.6%
👍2527.5%
❤1718.7%
👎11.10%
👏11.10%

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 91 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 24 March 2026 to 6 July 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.

Recent posts

6 Jul 2026, 16:12 UTC83 views4 reactionsread 9 August 2026

Shu bo'yicha texnik tavsiyalarim 1. Iloji boricha biznes logikalarni controller(server)dan boshqarish, client tarafga faqatgina o'zining mas'uliyatini qoldirish 2. Loglarni yozib borish, kutilmagan xatolarni ushlash uchun 3. Zarur bo'lmasa over-engineering qilmaslik xavfsizlik, clean code borasida. Birinchi o'ringa maximal darajada foydalanuvchining qulayligini qo'yish.

❤3🔥1

6 Jul 2026, 16:11 UTC82 views3 reactionsread 9 August 2026

Katta mas'uliyat olgandan so'ng xato qilishga berilgan imkon maximal kamayib boradi. To'g'ri xato hammada bo'ladi deb dalda berishilari mumkin lekin bu baribir xato. Pul qanchalik muhim bo'lmasin agar katta marra ko'zlangan bo'lsa asosiy o'ringa avtoritet, ishni ohirigacha bitira olish va mijozni rozi qilish chiqib boraveradi. Chunki aynan shu narsa o'ziga bo'lgan ishonchni olib keladi. Avvallari loyihada kamchilik…

❤3

3 Jun 2026, 21:07 UTC139 views6 reactionsread 9 August 2026

Siyqasi chiqish Ba'zida shunday holat bo'ladi bitta katta muammo atrofida o'ralashib qolaman. Men bilan ishlayotgan inson zerikib qolishi hech gap emas chunki bitta tushuntirilgan taskni qayta tushuntiraverish zeriktiradi. Lekin focus shu muammoni yechishda, zerikib qolishdan qochishda emas. Har safar muhokama qilinganida miyyada yangi tajriba paydo bo'laveradi va maummoni yanada aniqroq tushunib boriladi. Va ohiri…

🔥6

1 Jun 2026, 11:53 UTC130 views4 reactionsread 9 August 2026

Performance va User loveni oshirish bo'yicha bir nechta tavsiyalar 1. CDN ishlatish(Userlarga filelarni tezroq olib keladi va asosiy serverga requestlar kamayadi RAM, CPU, Network bandwith tejaladi) 2. Vaziyatga qarab responselarni asynxrom qilish(So'rovingiz qabul qilindi tayyor bo'lsa xabar beramiz. Bu orqali userni ko'p kuttirmasdan navbatba navbat ishlarni bajarib olsak bo'ladi) 3. Ilova/Website tarafda cache …

❤2👍2

24 May 2026, 03:05 UTC146 views6 reactionsread 9 August 2026
Photo

Work => Eat => Sleep => Repeat. Dasturchi hayoti 🥱.

👍4🔥2

23 May 2026, 08:33 UTC126 views5 reactionsread 9 August 2026
Photo

Kunduzi ko’chaga chiqmaganimga ancha bopti 😂

🔥3❤2

18 May 2026, 18:07 UTC142 views6 reactionsread 9 August 2026
Video message

Video message, posted without a caption

🔥5❤1

15 May 2026, 21:47 UTC156 views7 reactionsread 9 August 2026

Bugun 2 soat ichida mobile, web, backendda complex feature yozib uni test qildim feature tayyyor qanday qilib? Taskni to'liq tushunib oldim => enhanced prompt yozdim => plan tuzildi/implement qilindi => backend push bo'ldi => 1 minutdan keyin marionette mcp ishga tushib mobile appni testlashni boshladi (tugmalarni bosdi, screenshot olib UIni tekshirdi) => playwright mcp xuddi shuni web appda qildi. Hisobot yaratil…

👍4🔥2👎1

12 May 2026, 18:38 UTC153 views5 reactionsread 9 August 2026
Photo

Productiv kun ohirdagi dam olish. Ketadiyuui 😂😎

🔥5

9 May 2026, 20:36 UTC140 views6 reactionsread 9 August 2026
Photo

30 secund tahlil qildi tugmalarni bosib ko'rdi xullas to'liq tekshirib hisobot berdi. Bug fixlar uchun zo'r tool. Chunki inson factorini kamaytiradi harbir actionni o'zi qilib ko'radi real factni aytadi. Agar testing jarayonini automatlashtira olsam to'liq production ready ilova tayyor bo'ladi. Chunki feature yozish hozir oson lekin uni testlash qiyinroq.

👍5❤1

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

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

“Bekzod G‘ayratov” (@bekzod_gayratov), 70 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/bekzod_gayratov.

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.