Qurbon Hayit muborak, TJUG hamjamiyati! 🌙☕ Barchangizga tinchlik, baraka va mustahkam sog’lik tilaymiz! https://linktr.ee/tjug
👍13
Signed Иззатулла

Channel
@tashkent_jug
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
216subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003801528074 |
|---|---|
| Type | Channel |
| Username | @tashkent_jug |
| Created | 24 March 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 15 August 2026 |
| On Telegram | t.me/tashkent_jug |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 22:32 | 216 | -1 |
| 7 Aug 2026, 03:31 | 217 | no change |
| 6 Aug 2026, 22:46 | 217 | first reading |
13 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 pageof 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 13 posts for this entry, the most recent from 27 May 2026. An engagement rate over an empty window would be a number about nothing.
136 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 88 | 64.7% | |
| 🔥 | 32 | 23.5% | |
| 👌 | 5 | 3.68% | |
| 👏 | 5 | 3.68% | |
| ⚡ | 4 | 2.94% | |
| 🤔 | 1 | 0.735% | |
| 🫡 | 1 | 0.735% |
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 13 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 136reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 24 March 2026 to 27 May 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 @tashkent_jug. 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 13 most recent posts we hold for this entry, published 24 March 2026 to 27 May 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.
Qurbon Hayit muborak, TJUG hamjamiyati! 🌙☕ Barchangizga tinchlik, baraka va mustahkam sog’lik tilaymiz! https://linktr.ee/tjug
👍13
Signed Иззатулла
Atomicity nima ? Commentariyada to'liq tarif berilgan aynan menga yoqqan commentariya egasi bilan tekinga interview qilaman qolgan hohlovchilar uchun interview link - https://shaffof-prep-interview.uz/ Ertaga g'olibni aniqlaymiz @akhror_mamasodirov_97
👍4
Signed Izzatulla
🔥 TJUG #1 — That’s a Wrap! We had an amazing time bringing the community together — great talks, real insights, and strong vibes all around. Big thanks to everyone who joined and to our speakers for sharing their knowledge 🙌 🎥 Check out the highlights in this short video! Stay tuned… this is just the beginning 🚀 https://linktr.ee/tjug
👍16🔥2
Signed Izzatulla
Tashkent Java User Group pinned a photo
Thank you for being part of TJUG #1 It was amazing to see so many engineers come together for our very first meetup. Huge thanks to everyone who attended — your engagements made this event truly special. — 🎤 Special thanks to our speakers: • Sirojiddin Saidov • Javokhir Abdullaev • Azizbek Tuychiev • Jamshidbek Karimov • Shakhzod Murtazaev Thank you for your time, effort, and for sharing real-world knowledge with…
👍27👏5⚡4🫡1
Signed Izzatulla
⚠️⚠️⚠️ We encourage everyone to put REAL DATA in the forms, as you will be checked while entering the building!
👌4🤔1
Signed Izzatulla
🚀 TJUG #1 — Registration is now OPEN! 📅 Date: 25.04.2026 🕒 Time: 14:00 📍 Location: Toshkent shahar, Yashnobod tumani, Shahrisabz ko’chasi 87 We’re excited to invite you to the very first Tashkent Java User Group meetup. What to expect: • 5 strong speakers • real production experience • Java, Kafka, CI/CD, Performance and more ⚠️ Seats are strictly limited — registration will close once capacity is reached. Regi…
🔥8👍2
Signed Izzatulla
🎤 Final Speaker Announcement Meet: Shakhzod Murtazaev Senior Software Engineer at Anorbank 💬 Topic: Virtual Threads Without The Hype Virtual Threads are one of the most talked-about features in modern Java — but when should you actually use them? In this session, Shakhzod will cover: • what Virtual Threads really are (beyond the hype) • when they make sense — and when they don’t • how to use them effectively in r…
🔥7👍3
Signed Izzatulla
🎤 Speaker #4 is on board! Meet: Jamshidbek Karimov Senior Software Engineer | Yangi Texnologiyalar Ilmiy Axborot Markazi 💬 Topic: Why Your App Chokes at 200 Users: HikariCP Tuning Everything works fine… until real users arrive. In this session, Jamshidbek will cover: • why applications fail under moderate load • how connection pools actually behave • tuning HikariCP for real performance gains — We’re focusing o…
👍5
Signed Izzatulla
🎤 Speaker #3 is here Meet: Azizbek Tuychiev Head of Backend at Anorbank 💬 Topic: Kafka Without Pain: From Zero to Production Event-driven systems are powerful — but Kafka can be tricky if not done right. In this session, Azizbek will cover: • how to start with Kafka from scratch • designing reliable event-driven systems • avoiding common production pitfalls — We’re bringing together engineers who build real, sc…
👍7🔥3
Signed Izzatulla
🎤 Speaker #2 announced Meet: Javokhir Abdullaev Senior Software Engineer at EPAM Systems 💬 Topic: "From Zero to GitHub Actions" CI/CD is no longer optional — but many teams still struggle to implement it properly. In this session, Javokhir will cover: • how to get started with GitHub Actions from scratch • building real CI/CD pipelines step by step • common mistakes and how to avoid them — At TJUG, we focus on …
👍6🔥2
Signed Izzatulla
🚀 TJUG is launching — and we’re excited to introduce our first speaker Meet: Sirojiddin Saidov Senior Software Engineer at EPAM Systems 💬 Topic: “Mastering @Transactional in Spring Boot” Transactions are often misunderstood — until something breaks in production. In this session, We will break down: • how @Transactional really works under the hood • common pitfalls that even experienced developers make • how to d…
🔥10👍5👌1
Signed Izzatulla
Showing the 12 most recent of 13 posts we hold for @tashkent_jug. 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.
Citation-graph rank — 688,038 of 1,481,346entries 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Tashkent Java User Group” (@tashkent_jug), 216 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/tashkent_jug.
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.