Telegram RegisterThe public register of Telegram
Telegram profile photo for Yandex Uzbekistan for Developers

Channel

Yandex Uzbekistan for Developers

@yandexuzdev

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

3,174subscribers

-41 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002436958865
TypeChannel
Username@yandexuzdev
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live3 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/yandexuzdev

Growth

3,1463,2153,180.56 August 2026 — 3,215 subscribers6 August 2026 — 3,215 subscribers9 August 2026 — 3,212 subscribers12 August 2026 — 3,187 subscribers16 August 2026 — 3,183 subscribers19 August 2026 — 3,173 subscribers22 August 2026 — 3,160 subscribers25 August 2026 — 3,147 subscribers28 August 2026 — 3,146 subscribers31 August 2026 — 3,165 subscribers3 September 2026 — 3,174 subscribers3,1746 August 20263 September 2026
11 measurements spanning 28 days, net -41. 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 3,136–3,225 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 02:153,174+9
31 Aug 2026, 07:063,165+19
28 Aug 2026, 14:153,146-1
25 Aug 2026, 03:333,147-13
22 Aug 2026, 00:143,160-13
19 Aug 2026, 03:243,173-10
16 Aug 2026, 08:473,183-4
12 Aug 2026, 16:143,187-25
9 Aug 2026, 09:523,212-3
6 Aug 2026, 04:493,215no change
6 Aug 2026, 02:333,215first reading

Engagement

11 posts held, back to 2 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 11 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

387 reactions across 11 posts, in 15 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥14136.4%
👍6516.8%
6216.0%
👎4311.1%
💯287.24%
🎉164.13%
👏92.33%
🤩71.81%
🤝41.03%
❤‍🔥30.775%
🤡30.775%
🕊20.517%
😎20.517%
🆒10.258%
🙏10.258%

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 11 of the 11 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 387 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 2 July 2026 to 27 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

27 Jul 2026, 08:02 UTC≈2,060 views23 reactionsread 7 August 2026
Photo

Yaxshi tayyorgarlik suhbatdan bir kun oldin emas, balki muntazam mashq qilishdan boshlanadi 💬 Agar algoritmlarni takomillashtirmoqchi bo‘lsangiz, CodeRun’dagi vazifalar to‘plamimizni ko‘rib chiqing - u texnik suhbatlarga tayyorgarlik ko‘rish uchun juda mos keladi. Yandex Uzbekistan’da amaliyot o‘tash imkoniyatini qo‘ldan boy bermaslik uchun ta’lim dasturlarimiz e’lonlarini kuzatib boring! ➡️ Masalalar yechish ____

🔥117💯3👍2

24 Jul 2026, 10:20 UTC≈2,220 views22 reactionsread 7 August 2026
Photo

🌷 Suhbatdan so‘ng rekruterga nima yozishni bilmayapsizmi? Yoki sizga javob berishmasa, o‘zingizni qanday eslatib qo‘yish mumkin? Barcha holatlar uchun 10 ta xat shablonini tayyorladik: birinchi tanishuvdan tortib, suhbatdan keyingi kuzatuv va taklifga javobgacha. Maqolani o‘qish ↗️ Saqlab qo‘ying — ish qidirayotgan har bir kishiga asqotadi. ____ 🌻 Не знаете, что написать рекрутеру после собеседования? Или как нап

🔥133👍3👏2🤝1

22 Jul 2026, 06:34 UTC≈2,860 views15 reactionsread 7 August 2026
Video

O‘zbekiston transportini aqlliroq qilish uchun kod, ma’lumotlar va 72 soat ⭐️ O‘zbekiston Respublikasi Transport vazirligi bilan birgalikda ishtirokchilar transport sohasining haqiqiy vazifalari uchun raqamli yechimlarni ishlab chiqadigan National Transport Hackathon - xakatonni boshlaymiz. 6-8-avgust kunlari jamoalar uchta yo‘nalishdan birini tanlashlari mumkin: mobillik xizmatlari, Transport vazirligi tizimlari u

👍73🔥3🎉1🤝1

17 Jul 2026, 09:32 UTC≈3,140 views17 reactionsread 7 August 2026
Photo

📌 Yandex’da SI-agentlar qanday himoyalanishini aytib beramiz Agar kodlash uchun SI-agentlardan foydalansangiz va modellarga fayllaringizga kirish huquqini bersangiz, bu intensiv aynan siz uchun. 2026-yil 27–31-iyulda Yandex School of Data Analysis (YSDA) maktabining AI Agents Security Week haftaligi bo‘lib o‘tadi. Mutaxassislar zamonaviy SI-tizimlarni qanday qilib xavfsiz qilish haqida aytib berishadi. Dasturda: •

👍7🔥53🎉2

15 Jul 2026, 12:02 UTC≈3,260 views45 reactionsread 7 August 2026
Photo

11-iyul kuni IT Community a’zolarini Yandex Uzbekistan ofisiga nonushtaga taklif qildik ☕️ Karyera boshlash, amaliyot o‘tash va ish topish haqida suhbatlashdik: Ulug‘bek Baxtiyorov Yandex Go‘dagi tajribasi bilan o‘rtoqlashdi, Shahriyor Sobirov esa rezyumeni qanday mustahkamlash va global bozorda ajralib turish haqida so‘zlab berdi. Uchrashuv yangi ofis bo‘ylab ekskursiya va ishtirokchilar bilan norasmiy muloqot bila

🔥2110🎉6❤‍🔥3👍2🤝2🆒1

13 Jul 2026, 08:51 UTC≈2,210 views36 reactionsread 7 August 2026
Photo

Talaba ➡️ Vakil + Amaliyotchi Bahorda Jasmina Inha universitetida Yandex Uzbekistan elchilari dasturiga qo‘shildi va bugungi kunda u Yandex Pro sinov jamoasida amaliyot o‘tamoqda. Kartochkalarda u qanday qilib bo‘sh ish o‘rniga murojaat qilishga qaror qilgani, tanlovning qanday bosqichlaridan o‘tgani va amaliyot qanday o‘tayotgani haqida so‘zlab beradi. Tezroq kartochkalarni o‘qing — ehtimol, bu hikoya karyerangiz

🔥176🎉6🤡3👍2🕊2

6 Jul 2026, 10:51 UTC≈3,030 views68 reactionsread 7 August 2026
Video message

Video message, posted without a caption

👎24🔥23👍108👏3

6 Jul 2026, 10:49 UTC≈3,000 views19 reactionsread 7 August 2026

👉 Bitta to‘g‘ri savol jamoaning bir necha kunlik ishini tejashi mumkin! A’zam Qahramoni nima uchun vazifani tushunish qobiliyati dasturchilar uchun raqobatbardosh ustunlikka aylanishini va bu ko‘nikma kasbda o‘sishga qanday yordam berishini tushuntiradi. Odatda yangi vazifa ustida ishlashni qanday boshlaysiz - darhol kod yozasizmi yoki avval kontekstni tushunib olasizmi? 💬 ____ 👉 Один правильный вопрос может сэкон

🔥94👍4🎉1👎1

2 Jul 2026, 09:18 UTC≈3,310 views60 reactionsread 7 August 2026
Video message

Video message, posted without a caption

💯23👍12👎98👏3🔥2😎2🙏1

2 Jul 2026, 09:13 UTC≈3,170 views62 reactionsread 7 August 2026
Video message

Video message, posted without a caption

🔥32👍119👎8💯2

2 Jul 2026, 09:12 UTC≈3,190 views20 reactionsread 7 August 2026

💬 Keling, muhokama qilamiz: bugungi kunda dasturchi uchun nima muhimroq — kod yozishmi yoki sun’iy intellekt bilan ishlay olishmi? Tadbirkor, o‘qituvchi va Englify School asoschisi A’zam Qahramoniy bilan birgalikda bugungi kunda IT sohasida karyera qurayotgan har bir kishini tashvishga solayotgan mavzularni ko‘rib chiqamiz. Muhokamaga qo‘shiling va fikrlaringizni izohlar bo‘limida baham ko‘ring! ____ 💬 Давайте обс

🤩7👍5🔥51👎1👏1

Showing the 11 most recent of 11 posts we hold for @yandexuzdev. 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

Named by 13 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.

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.

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

“Yandex Uzbekistan for Developers” (@yandexuzdev), 3,174 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/yandexuzdev.

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.