Telegram RegisterThe public register of Telegram

Channel

Data Day

@dataday_official

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

1,076subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002520821538
TypeChannel
Username@dataday_official
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dataday_official

Growth

1,0751,0771,0766 August 2026 — 1,077 subscribers7 August 2026 — 1,075 subscribers14 August 2026 — 1,076 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 1,075–1,077 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 06:051,076+1
7 Aug 2026, 14:181,075-2
6 Aug 2026, 14:511,077first reading

Engagement

14 posts held, back to 9 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
21.6%
avg views ÷ 1,076 subscribers
Avg views / post
233
3 posts measured
Reaction rate
1.40%
reactions ÷ views · ER floor
Posts in window
3
of 14 held

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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held14 (9 July 20266 August 2026)
Views total698
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:51 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.

Reaction mix

59 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2033.9%
👍1728.8%
1627.1%
👏46.78%
💯23.39%

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

Measured over the 14 most recent posts we hold, published 9 July 2026 to 6 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.

Recent posts

6 Aug 2026, 10:07 UTC126 viewsread 6 August 2026

🤖 ИИ в банках обсуждают как продукт для клиентов и как способ оптимизации внутренних операций. Но заметно реже — как инструмент самого руководителя. На Форуме Data Day 2026 прозвучала важная мысль: ИИ для топ-менеджера — это уже не ChatGPT для подготовки писем. Это новая операционная модель, в которой руководитель работает не только с людьми, но и с цифровыми исполнителями. При этом есть разрыв: банки активно инв

4 Aug 2026, 08:35 UTC206 views4 reactionsread 6 August 2026
Video

5-й форум Data Day 2026 зарекомендовал себя как главное место встречи экспертов и лидеров всего рынка, работающих с данными. Сегодня событие охватывает самые разные отрасли — от ритейла и агропромышленности до образования и финтеха. Участники обсуждали, как с помощью данных строить точные прогнозы, минимизировать риски, оптимизировать бизнес-процессы и находить новые точки роста. «Многие коллеги смогут здесь найти д

👍2👏1🔥1

21 Jul 2026, 12:58 UTC366 views4 reactionsread 6 August 2026
Photo

ИИ масштабирует не только эффективность, но и последствия. Готовы ли ваши данные к эпохе автономных агентов? Одно дело, когда аналитический вывод читает человек — он может заметить противоречие и запросить проверку. Совсем другое, когда ИИ-агент сам принимает решения в реальном времени: заказывает товар, меняет логистический маршрут, формирует предложение или оценивает риски. В этой точке качество данных из ИТ-мет

🔥2👍1👏1

14 Jul 2026, 12:05 UTC493 views9 reactionsread 6 August 2026
Photo

Инсайты HeadExpert на Data Day 2026: как управление данными трансформируется в управление компанией? Как меняется роль CDO в компаниях, которые уже работают с ИИ – или готовятся масштабировать его в ближайшие годы? Этот вопрос был ключевым для участников дискуссии NEXT CDO на Форуме Data Day, который состоялся 9 июля. Главный вывод: Функция данных сохраняет свой классический фундамент (платформа, качество, доступы

👍3🔥32👏1

13 Jul 2026, 11:06 UTC386 views7 reactionsread 6 August 2026
Photo

Друзья, 9 июля состоялся 5-й Форум Data Day 2026. Впечатляющие итоги в цифрах: 2000+ участников 5 отраслевых треков 90+ спикеров 👉 Подробности в пострелизе по ссылке Ниже - ключевые тезисы из обсуждений экспертов: 1️⃣Качество данных важнее доступности ИИ: сам по себе искусственный интеллект не исправляет слабые бизнес-процессы, а лишь масштабирует хаос. Без надежного фундамента данных алгоритмы бессильны. 2️⃣Без

4👍2🔥1

9 Jul 2026, 15:25 UTC474 views7 reactionsread 6 August 2026
Photo

Data Day успешно завершен! Благодарим всех участников и ждем вас на следующих мероприятиях: InsurtechDay 23 июля 2026 / Бизнес.Техноград Scoring Day 24 сентября / Москва Форум лидеров страхового рынка 29 октября / Центр событий РБК

7

9 Jul 2026, 14:40 UTC483 views3 reactionsread 6 August 2026
Photo

📸Друзья, перед уходом обязательно загляните к доске с магнитами у выхода. В течение дня на площадке работают фотографы — возможно, ваше фото уже ждет вас там. Найдите свой снимок, заберите его с собой и сохраните яркое воспоминание об этом дне!

🔥21

9 Jul 2026, 14:30 UTC445 views5 reactionsread 6 August 2026
Photo

Стартовала завершающая сессия NEXT CDO: следующее поколение директоров по управлению данными. На базе исследования HeadExpert, Aston, Deco Systems и Ассоциации больших данных спикеры обсуждают, как ИИ меняет роль CDO: от управления качеством данных — к управлению доверием к данным, моделям и решениям.

👍3👏1🔥1

9 Jul 2026, 13:54 UTC456 views2 reactionsread 6 August 2026

Форум проходит бодро, обстановка на треке Путешествия и транспорт - ламповая! Делится впечатлениями Александр Аралов, директор по аналитике и управлению данными, Туту.

👍2

9 Jul 2026, 13:54 UTC482 views1 reactionsread 6 August 2026
Video message

Video message, posted without a caption

🔥1

9 Jul 2026, 13:28 UTC474 views4 reactionsread 6 August 2026

Павел Денисенко, директор департамента развития платформы больших данных X5 Tech, модератор трека «Ритейл» - о том, чьи выступления произвели наиболее сильное впечатление

2💯2

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

Citation-graph rank — 58,601 of 1,480,688entries 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.

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

“Data Day” (@dataday_official), 1,076 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dataday_official.

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.