Telegram RegisterThe public register of Telegram
Telegram profile photo for Big Data AI

Channel

Big Data AI

@bigdatai

On this record: Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

18,192subscribers

+22 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001684696497
TypeChannel
Username@bigdatai
Description@haarrp - админ Вопросы с собеседований по Machine Learning, Data Science, Deep Learning и Нейроннным сетям @data_analysis_ml - анализ данных @ai_machinelearning_big_data @itchannels_telegram - важное для программиста РКН: clck.ru/3Fmqxe
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live23 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/bigdatai

Growth

18,13418,19218,1636 August 2026 — 18,170 subscribers6 August 2026 — 18,170 subscribers6 August 2026 — 18,161 subscribers7 August 2026 — 18,156 subscribers8 August 2026 — 18,152 subscribers9 August 2026 — 18,148 subscribers10 August 2026 — 18,145 subscribers11 August 2026 — 18,143 subscribers12 August 2026 — 18,142 subscribers13 August 2026 — 18,141 subscribers14 August 2026 — 18,134 subscribers16 August 2026 — 18,137 subscribers17 August 2026 — 18,140 subscribers18 August 2026 — 18,137 subscribers19 August 2026 — 18,140 subscribers20 August 2026 — 18,146 subscribers22 August 2026 — 18,149 subscribers23 August 2026 — 18,192 subscribers6 August 202623 August 2026
18 measurements spanning 18 days, net +22. 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 18,125–18,201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 20:0318,192+43
22 Aug 2026, 02:2618,149+3
20 Aug 2026, 20:3418,146+6
19 Aug 2026, 18:2618,140+3
18 Aug 2026, 15:5418,137-3
17 Aug 2026, 17:4618,140+3
16 Aug 2026, 14:0518,137+3
14 Aug 2026, 23:1618,134-7
13 Aug 2026, 16:1618,141-1
12 Aug 2026, 12:5818,142-1
11 Aug 2026, 15:1818,143-2
10 Aug 2026, 16:3618,145-3
9 Aug 2026, 19:0318,148-4
8 Aug 2026, 18:4018,152-4
7 Aug 2026, 17:4118,156-5
6 Aug 2026, 20:4018,161-9
6 Aug 2026, 02:1618,170no change
6 Aug 2026, 01:5018,170first reading

Engagement

43 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 36 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.12%
avg views ÷ 18,192 subscribers
Avg views / post
1,290
32 posts measured
Reaction rate
0.546%
reactions ÷ views · ER floor
Posts in window
32
of 43 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 30 of 32 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 21 August 2026
Posts held43 (9 July 202621 August 2026)
Views total41,435
Reactions total215
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Aug 2026, 22:44 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.

What this channel posts

Photos
1,110
Videos
161
Links
1,110

Lifetime counters from Telegram’s own channel header, read 23 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
7m 53s
Average length
1m 58s

Measured directly from 4 videos 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

304 reactions across 39 posts, in 14 distinct kinds. The most used accounts for 31.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
9731.9%
👍6722.0%
😁6120.1%
🔥3511.5%
🙈92.96%
🥰72.30%
🤔61.97%
💯51.64%
🤡51.64%
👀30.987%
👎30.987%
🤣30.987%
🥱20.658%
🤮10.329%

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

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

Advertising

Ad load
9.30%
4 of 43 posts carry an ad marker
Regulatory tokens
4
posts carrying an erid · 4 distinct tokens
Median views · ads
927
over 4 measured posts
Median views · rest
1,450
over 39 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VtzqxRy2AP118 August 202618 August 2026
2VtzqxjjqGo113 August 202613 August 2026
2W5zFGUGZzq117 August 202617 August 2026
2W5zFJtGMPF118 August 202618 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 43 most recent posts we hold, published 9 July 2026 to 21 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

21 Aug 2026, 12:01 UTC673 views6 reactionsread 23 August 2026
Video

☁️☁️☁️☁️☁️☁️☁️ Yandex Cloud 24 сентября проведёт флагманскую конференцию в Москве — Yandex Scale 2026. 🎨🎨🎨🎨🎨🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨🎨🎨🎨🎨 В программе четыре продуктовых трека — AI, Data, Security и Hybrid Infrastructure & DevOps, — и отдельный углублённый технологический трек DeepTech, который пройдёт только онлайн. В треке AI откроем программу докладом о том, как развиваются платформы для создания ИИ-агентов и рынок

👍41🔥1

21 Aug 2026, 11:07 UTC682 views6 reactionsread 23 August 2026
Photo

⚡️ SenseNova U1.5-Lite: не «умеет всё», а умеет делать всё вместе SenseNova выпустила U1.5-Lite - открытую мультимодальную модель на 8B параметров для понимания изображений, генерации и редактирования. Главная идея здесь не в размере, а в объединении навыков в одной модели. U1.5-Lite умеет работать со сложными промптами, нативно генерировать 2K/4K, лучше рисовать текст и делать локальные правки без отдельного роут

👍32🔥1

20 Aug 2026, 16:36 UTC791 views2 reactionsread 23 August 2026
Photo

На старте ИИ-проекта для инференса часто используют API ⤵️ Но по мере роста нагрузки, требований к безопасности и затрат возникает потребность в собственной ИИ-инфраструктуре. На вебинаре 25 августа эксперты Cloud․ru расскажут, когда пора переходить на Bare Metal и как построить инфраструктуру для запуска моделей в продакшене. В программе: ▶️Когда для инференса достаточно API, а когда переходить на собственную инф

1👍1

20 Aug 2026, 10:31 UTC805 views2 reactionsread 23 August 2026
Forwarded from @rust_codePhoto

⚡️ Переписывание Bun на Rust превращается в очень странный AI-эксперимент Bun 1.4 задерживается уже около трёх месяцев, и автор Tero Piirainen считает, что проблема намного интереснее обычного сорванного релиза. За последний месяц в репозитории Bun 15,8 тыс. коммитов сделал robobun, ещё 1,6 тыс. — autofix-ci[bot], а Jarred Sumner — около 790. При этом у проекта накопилось больше 5 тыс. открытых PR. По сути, Bun ст

2

19 Aug 2026, 14:25 UTC894 views8 reactionsread 23 August 2026
Photo

Ornith-1.5: новая семья open-source моделей с упором на самообучение В линейку вошли три версии: 9B Dense, 35B MoE и 397B MoE. Авторы делают ставку не только на масштаб, но и на self-improvement: модель сама предлагает новые задачи, строит под них scaffolding и генерирует rollouts для последующего RL-обучения. По заявленным результатам, Ornith-1.5 показывает сильные цифры на reasoning, coding и agentic-бенчмарках:

3👍3🥰2

18 Aug 2026, 13:03 UTC≈1,020 views9 reactionsread 23 August 2026
Advertisementerid 2VtzqxRy2APPhoto

Вырастили целое дерево из агентов 🌳 Мы в Авито разработали единую платформу для процессов. Самые лучшие и популярные становятся агентами. В итоге каждый сотрудник может создать свой процесс или воспользоваться готовым. Классно? Не то слово! Поэтому мы написали статью, как создавали это решение. О чём узнаете, если прочитаете: 🔸как устроена архитектура платформы, 🔸как процесс становится агентом, 🔸как измерять качест

3👍2🔥2🤡2

18 Aug 2026, 11:45 UTC597 views12 reactionsread 23 August 2026
Forwarded from @ai_machinelearning_big_dataVideo

✔️ США пригрозили исключать из Pax Silica страны, работающие с КНР по ИИ Госдепартамент разослал странам-партнерам документ с требованием свернуть сотрудничество с Китаем в сфере ИИ. Кто откажется - вылетит из Pax Silica, коалиции, созданной ради контроля над поставками полупроводников, ИИ-технологий и критических минералов. Поводом стали действия Казахстана, крупного поставщика редкоземельных ископаемых. Страна по

6👍3🥰3

18 Aug 2026, 09:45 UTC788 views2 reactionsread 23 August 2026
Advertisementerid 2W5zFJtGMPFPhoto

Компании финансового и промышленного секторов уже активно внедряют технологии машинного обучения (МL) 👨🏻‍💻И правильно, ведь это повышает эффективность бизнес-процессов и позволяет создавать новые цифровые сервисы. ☹️Но высокие операционные риски, большие затраты на вывод моделей в промышленную эксплуатацию (и еще ряд проблем) мешают масштабированию ML-проектов. 😊Эти задачи решает продукт с говорящим названием "Упра

2

18 Aug 2026, 09:32 UTC868 views8 reactionsread 23 August 2026
Photo

🚀 DeepSeek V4 Pro внезапно стал заметно сильнее - без переобучения модели К DeepSeek V4 Pro 0813 подключили harness под названием J-Space, который снижает ошибки в длинных цепочках reasoning и tool use. По опубликованным результатам прирост местами очень серьёзный: * Terminal Bench: 87.9 → 90.1 * NL2Repo: 61.5 → 73.4 * CyberGym: 83.3 → 86.8 * DeepSWE: 62.7 → 72.0 * Toolathlon: 74.1 → 79.5 В ряде agentic/coding те

4🤣3😁1

17 Aug 2026, 10:00 UTC927 viewsread 23 August 2026
Advertisementerid 2W5zFGUGZzqPhoto

17 сентября собираем всех, кто реально делает ИИ, на AI R&D DAY в Москве. Конференция для R&D-специалистов, AI-архитекторов, продакт-менеджеров и технических лидеров, отвечающих за внедрение технологий следующего поколения. Особенности программы: 🔹 NextGenAI: из исследований — в продукты 🔹 Голос, текст, изображения, звук — в одной системе 🔹 Как оценивать качество, когда старые метрики устарели 🔹 22 доклада от тех,

16 Aug 2026, 10:49 UTC≈1,000 views9 reactionsread 23 August 2026
Photo

🇪🇺 Китайские open-weight модели начинают всё активнее заходить в европейский enterprise. Siemens уже рассказывала о собственной изолированной LLM-платформе на базе vLLM, куда можно подключать Qwen, DeepSeek, Llama и другие открытые модели без привязки к одному API. Данные можно оставить внутри собственной инфраструктуры. Если персональные данные не уходят внешнему провайдеру за пределы EEA, не возникает отдельного

4👍4🤔1

Showing the 12 most recent of 43 posts we hold for @bigdatai. 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 — 91,195 of 1,585,381entries 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 45 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Искусственный интеллект. Высокие технологии
@vistehno · 72,222
Telegram ranks this channel #8 of 94 here — alongside 93 others — read 20 August 2026
Python/ django
@pythonl · 58,935
Telegram ranks this channel #13 of 84 here — alongside 83 others — read 22 August 2026
Machinelearning
@ai_machinelearning_big_data · 284,523
Telegram ranks this channel #37 of 95 here — alongside 94 others — read 10 August 2026
Kali Linux
@linuxkalii · 55,091
Telegram ranks this channel #79 of 89 here — alongside 88 others — read 23 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Big Data AI” (@bigdatai), 18,192 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/bigdatai.

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.