Channel
@veklichbot
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,430subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001719198648 |
|---|---|
| Type | Channel |
| Username | @veklichbot |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/veklichbot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 15:16 | 1,430 | +2 |
| 2 Sept 2026, 11:16 | 1,428 | +1 |
| 30 Aug 2026, 19:34 | 1,427 | +2 |
| 27 Aug 2026, 11:55 | 1,425 | -1 |
| 24 Aug 2026, 09:44 | 1,426 | +4 |
| 20 Aug 2026, 17:24 | 1,422 | +2 |
| 18 Aug 2026, 03:28 | 1,420 | +1 |
| 11 Aug 2026, 15:23 | 1,419 | -1 |
| 8 Aug 2026, 20:52 | 1,420 | -3 |
| 6 Aug 2026, 07:49 | 1,423 | no change |
| 6 Aug 2026, 01:11 | 1,423 | first reading |
4 posts held, back to 1 July 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 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 4 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
Пресс-служба Telegram должна доплачивать мне за такие интервью, думаю 🤣 А кто еще расскажет на американскую аудиторию, что делать ботов и агентов тут — это новый уровень и новый рынок с лучшей технической инфраструктурой. Чего только стоит рост @botfather с 3 млн до 11 млн MAU после выхода OpenClaw! В общем, приятно быть в авангарде! Работаем над репутацией Telegram дальше. Читать: https://www.unite.ai/anna-vekli…
OpenAI, Revolut, Nebius и мы на одной сцене 🚀 Могла ли я подумать еще пару лет назад, что наша компания GPT4Telegrambot будет представлена на одной сцене с мировыми гигантами? Конечно нет. Но это так. На выходных в Белграде прошел финал Midnight Code Cup 2026 — соревнование по программированию для самых талантливых ребят со всего мира. 500 команд на старте, 29 команд финалистов, сложнейшие технические задачи и инже…
Артличный эффект Аню знаю давно. Со времён когда она руководила продвижением и приемной кампанией ИТМО, была помощником ректора по PR. Это Аня придумала девизы «Первый неклассический», «Поступай не как все», «Больше чем университет» / «IT's MOre than a UNIVERSITY!». Позже уехала работать в Москву. Работала в консалтинге для разных вузов. В 2022 году с семьей переехала в Берлин. И вместе с мужем и племянником созд…
ClickClick — your deck is done Запустили свой сервис презентаций ClickClick. 🚀На наш взгляд это намного круче всего, что есть на рынке: — Топовый дизайн, который вы нигде не найдете — Актуальная информация, структура и высокое качество контента — Не нужно ничего менять руками, просто пишете в чат правки и получаете обновлений вариант — Можно делать в стиле вашей компании (но тут пока не на 100%) ❓ Как создать 1.…
Showing the 4 most recent of 4 posts we hold for @veklichbot. 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.
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.
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.
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.
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Веклич + | -” (@veklichbot), 1,430 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/veklichbot.
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.