Telegram RegisterThe public register of Telegram
Telegram profile photo for AIDOL

Channel

AIDOL

@aidolrobot

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

493subscribers

-7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002746307461
TypeChannel
Username@aidolrobot
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/aidolrobot

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 89% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

493500496.56 August 2026 — 500 subscribers7 August 2026 — 499 subscribers27 August 2026 — 498 subscribers12 September 2026 — 493 subscribers6 August 202612 September 2026
4 measurements spanning 37 days, net -7. 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 492–501 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 10:02493-5
27 Aug 2026, 23:19498-1
7 Aug 2026, 00:17499-1
6 Aug 2026, 18:46500first reading

Engagement

9 posts held, back to 16 April 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 page 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 9 posts for this entry, the most recent from 1 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

229 reactions across 9 posts, in 10 distinct kinds. The most used accounts for 36.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8336.2%
🔥8034.9%
4218.3%
👏83.49%
👀62.62%
😁41.75%
🗿31.31%
👎10.437%
😍10.437%
🙏10.437%

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

Measured over the 9 most recent posts we hold, published 16 April 2026 to 1 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

1 Jul 2026, 08:37 UTC≈1,660 views21 reactionsread 6 August 2026
Photo

Айдол вышел в город 🤖 С сегодняшнего дня наш робот начал официальное пилотирование в культурно-досуговом центре в парке Ходынское поле. Приглашаем всех желающих зайти в гости, познакомиться с роботом, узнать больше о мероприятиях центра и просто задать ему любые вопросы. До встречи!

🔥9👍54🗿3

26 Jun 2026, 12:13 UTC490 views17 reactionsread 6 August 2026
Video

Айдол отправляется на пилотирование в парк Ходынское поле Впереди новый городской сценарий, где робот будет работать в месте с высокой проходимостью людей, встречать посетителей, помогать с навигацией, консультацией по мероприятиям и отвечать на вопросы в живом диалоге Для нас это важный шаг, когда робот из лаборатории и выставочных площадок переходит в реальную среду, где каждый день новые люди, новые запросы и но

👍10😁4👏3

19 Jun 2026, 12:32 UTC≈2,190 views25 reactionsread 6 August 2026
Video

«Привет! Всё ещё создаёте ИИ-агентов с помощью этих дефицитных устройств? Они Вам больше не нужны» 😉 Мы продолжаем развивать сценарии применения робота Айдол и показываем, как он может стать новым интерфейсом для работы с умными системами. Без ноутбуков, кода и сложных интерфейсов. Только голос и понятная задача. В видео показываем кейс офисного консьержа: робот помогает подготовиться к встрече, подключает нужные с

👍16🔥5👀31

10 Jun 2026, 13:58 UTC706 views16 reactionsread 6 August 2026
Photo

Сегодня мы провели закрытую встречу с нашим роботом Айдолом в офисе друзей АО «Р7». На одной площадке мы собрали представителей из разных сфер: банки, девелоперы, разработчики, ритейл бизнес, интеграторы, телеком и органы власти. Спасибо всем участникам, было приятно встретиться и познакомиться вживую 🙏🏼 На встрече мы протестировали диалоговые способности робота (Smart Dialogue System) и обсудили кейсы применения:

👍12🔥31

6 Jun 2026, 14:25 UTC593 views18 reactionsread 6 August 2026
Video

Петербургский форум подходит к концу. Мы благодарим организаторов форума и гостей за чудесную атмосферу А как приятно встречать таких красивых гостей!✨ На стенде ПМЭФ-2026 робот Айдол консультирует гостей о работе форума и проекта Здоровое общество Более того, в рамках медицинского кейса 🏥, робот может: - Встречать гостей - Консультировать по работе медицинского учреждения - Записывать к врачу - Собирать первичный

9👍7👀1🔥1

3 Jun 2026, 05:26 UTC593 views20 reactionsread 6 August 2026
Photo

Всем привет! Мы начинаем работу на Петербургском международном экономическом форуме - 2026! В этом году наш робот находится на стенде проекта «Здоровое общество» Будем рады видеть всех гостей 😉

🔥14👍51

30 May 2026, 05:09 UTC≈2,260 views27 reactionsread 6 August 2026
Photo

И еще одна отличная новость! Мы приняли участие в StartupVillage 2026, где подписали соглашение с Московским инновационным кластером и АНО «Развитие парков» о проведении пилотирования нашего настольного робота в Ходынском Поле 🦾 Робот будет встречать гостей, рассказывать про мероприятия, отвечать на вопросы и помогать с навигацией Продолжаем работать в этом направлении!

14👍9👏3🔥1

29 May 2026, 09:19 UTC605 views28 reactionsread 6 August 2026
Photo

Продолжаем делиться хорошими новостями 😉 Мы получаем оставшиеся зарегистрированные патенты на разработки Айдол, и еще сильнее закрепляем собственную технологическую базу 🦾 Для нас это не просто юридический этап, а важная часть большого пути! Дальше - больше!

🔥15👍82👀2👏1

16 Apr 2026, 07:25 UTC885 views57 reactionsread 6 August 2026
Photo

У нас отличные новости! Первая партия наших роботов скоро отправится в страну восходящего солнца! В Японию! 🇯🇵 Это особенно важный момент - первый экспортный контракт в сфере антропоморфной робототехники. Для нас это большая ценность и подтверждение того, что мы движемся в правильном направлении Мы с большим энтузиазмом смотрим на наше партнерство и будем рады развивать его вместе, создавая новые совместные проект

🔥32👍1110👎1👏1😍1🙏1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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.

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

“AIDOL” (@aidolrobot), 493 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/aidolrobot.

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.