Channel
@datacommunityuz
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,005subscribers
+26 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002449788923 |
|---|---|
| Type | Channel |
| Username | @datacommunityuz |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/datacommunityuz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 22:15 | 1,005 | +24 |
| 14 Aug 2026, 18:12 | 981 | +1 |
| 7 Aug 2026, 10:16 | 980 | +1 |
| 7 Aug 2026, 00:32 | 979 | first reading |
7 posts held, back to 21 April 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 7 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
104 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 56.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 59 | 56.7% | |
| 🔥 | 29 | 27.9% | |
| custom 5370980663778351052 | 8 | 7.69% | |
| 👏 | 8 | 7.69% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 7 of the 7 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 104reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 21 April 2026 to 21 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.
📊Ищем будущих Data Analysts! Открыт набор на Data Analytics 3.0 — бесплатную образовательную программу от TBC Uzbekistan. Если вы хотите развиваться в анализе данных, работать с реальными бизнес-задачами и учиться у экспертов одной из крупнейших финтех-команд региона — эта программа для вас. За 5 месяцев вы получите практические навыки работы с базами данных, SQL, Excel и Python, изучите статистику, A/B-тестирован…
❤12👏3🔥3
Митап #11 прошел очень бодро. До того самого матча Узбекистана с Португалией мы успели собрать хороший вечер, а после город моментально переключился в футбольный режим. Презентации спикеров можно скачать здесь: https://drive.google.com/drive/folders/1migkyKO-5_J_lMYxhD2geH1-Xl6mHn9M?usp=sharing Data Community Uz Telegram | LinkedIn
❤14
⚽️ Мы спланировали тайминг митапа так, чтобы успеть к началу футбола. Так что обязательно приходите, чтобы узнать новое о Data Lakehouse и пообщаться. Зарегистрируйтесь в боте — https://t.me/uzeventsbot. Участие бесплатное. 📅 23 июня 2026 (вторник) 🧭 19:00–21:00 🏫 School 21 (Ташкент, Зиёлилар, 13, ориентир — Университет Инха) 🗣 Язык: русский Data Community Uz Telegram | LinkedIn
🔥12❤4
Posted without readable text
❤7
Data Lakehouse в 2026 году Прошёл год с нашего митапа о Data Lakehouse — это направление развивается, поэтому наш следующий митап 23 июня будет посвящен современным compute-движкам и передовым платформам управления данными. В программе встречи: ✔️Обзор движков работы с данными и построения Lakehouse Разберём движки для работы с данными, их различия, сильные и слабые стороны. Сравним производительность Spark, Starro…
🔥8👏5❤4
Митап про ETL в эпоху AI: как это было Стало очевидно: переход от классических пайплайнов к новым подходам (и попытки внедрить туда AI) — это сейчас задача номер один для дата-команд. Чем особенно запомнился вечер: ✔️Говорили о компромиссах, ограничениях legacy-кода и о том, почему старые подходы перестают работать при росте данных ✔️Участники пришли с конкретными задачами из своих проектов. Никаких вопросов «для г…
❤18🔥6custom 53709806637783510524
Встречаемся сегодня на митапе Data Community. Поговорим про будущее ETL: как меняются инструменты, почему классические пайплайны перестают масштабироваться, что дают metadata-driven подходы и как AI влияет на разработку data-процессов. В программе — обзор ETL-ландшафта, кейс payme о переходе от legacy Python-пайплайнов к metadata-driven архитектуре и разбор того, почему команды начинают строить собственные ETL-решен…
custom 53709806637783510524
Showing the 7 most recent of 7 posts we hold for @datacommunityuz. 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 — 552,941 of 1,584,142entries 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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Data Community Uz” (@datacommunityuz), 1,005 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/datacommunityuz.
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.