Платежи через Cryptobot временно недоступны. Вместо него теперь xRocket. P.S. В работе сейчас большое обновление. Подготовительные работы на сервере завершены, потихоньку буду обновлять API, затем новые фичи в бота UPD: Cryptobot снова доступен. Аккаунт был заморожен после перевода с кошелька xRocket, поддержка ответила через ~24 часа.

Channel
Ход разработки Аналитика Telegram
@telesint
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Cite this entry
27,415subscribers
+3,574 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 | -1001467794188 |
|---|---|
| Type | Channel |
| Username | @telesint |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 20 October 2026 |
| Measurements held | 45 |
| Confirmed unchanged | 1 time, most recently 20 October 2026 |
| On Telegram | t.me/telesint |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Oct 2026, 12:38 | 27,415 | +83 |
| 19 Oct 2026, 13:18 | 27,332 | +47 |
| 18 Oct 2026, 14:20 | 27,285 | +59 |
| 17 Oct 2026, 12:34 | 27,226 | +49 |
| 16 Oct 2026, 11:19 | 27,177 | +39 |
| 15 Oct 2026, 14:29 | 27,138 | +62 |
| 14 Oct 2026, 14:19 | 27,076 | +83 |
| 13 Oct 2026, 04:58 | 26,993 | +234 |
| 8 Oct 2026, 20:22 | 26,759 | +104 |
| 4 Oct 2026, 07:15 | 26,655 | +160 |
| 25 Sept 2026, 17:19 | 26,495 | +435 |
| 19 Sept 2026, 01:21 | 26,060 | +94 |
| 16 Sept 2026, 18:18 | 25,966 | +88 |
| 14 Sept 2026, 20:58 | 25,878 | +69 |
| 13 Sept 2026, 10:21 | 25,809 | +93 |
| 11 Sept 2026, 16:39 | 25,716 | +204 |
| 9 Sept 2026, 06:15 | 25,512 | +179 |
| 5 Sept 2026, 21:40 | 25,333 | +116 |
| 3 Sept 2026, 22:00 | 25,217 | +88 |
| 2 Sept 2026, 11:22 | 25,129 | first reading |
Engagement
21 posts held, back to 9 January 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 105 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 27.5%
- avg views ÷ 27,415 subscribers
- Avg views / post
- 7,540
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 21 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.
| Window | Rolling 30 days · latest post in window 7 October 2026 |
|---|---|
| Posts held | 21 (9 January 2026 – 7 October 2026) |
| Views total | 30,150 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Oct 2026, 03:53 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
- Video runtime
- 4m 38s
- Average length
- 4m 38s
Measured directly from 1 video 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.
Recent posts
Продлил премиумы на 2 дня за субботу и воскресенье
Потихоньку восстанавливаются сервисы. Получилась неприятная история. Вчера один из сервисов допустил всплеск нагрузки и за пару часов нагегерировал несколько сотен! гигабайт логов, чем забил системный диск и положил сервер. Следующим утром я изменил конфигурацию контейнеров, ограничив размеры логов, все почистил и думал, что на этом закончил. А уже этой ночью другой сервис вновь допустил всплеск нагрузки из-за глуп…
Сервер, api и бот временно недоступны. Разбираюсь в проблеме. Возможно, до вечера будут недоступны 😢
Решил оставить 30%. Несправедливо, когда у всех ~30%, а у меня было 15%
Открыл доступ к API для всех пользователей, ранее он был доступен только по заявкам. Доступно по нажатию кнопки 👤 Профиль ➡️ 🔗API на клавиатуре в боте. Документация и цены тут: https://docs.telesint.dev Важно: подписка в боте никак не влияет на баланс API, в данный момент рефералка не распространяется на платежи за API.
🔥 У владельцев зеркал появился новый инструмент для сохранения и развития аудитории. Переходник - это отдельный бот, единственной задачей которого является выдача пользователю актуальной ссылки на сервис. Если текущее зеркало станет недоступно, переходник сам сообщит об этом всем пользователям заблокированного зеркала и выдаст ссылку на новое. Для владельцев зеркал: ➖ Переходник можно создать в разделе зеркал ➖ ❗️К…
Лето ☀️ Пора отпусков и... рефералок 💲 Мы запускаем летнее усиление реферальной программы: теперь выплаты за приглашённых пользователей станут до 2-х раза выше. Теперь базовый реферальный процент - 30%! А ещё — спойлер для владельцев зеркал 👀 Скоро появится новый функционал, который поможет эффективнее работать с аудиторией: вы сможете продвигать свои каналы через специальные переходники 🚀
Потихоньку восстанавливаемся. Часть сервисов уже работает, часть восстановится когда посплю 😴
API и бот остановлены. Переезжаю на новый сервер.
Временно остановил все тяжелые задачи. Обновление базы данных, расширенная выгрузка новых для сервиса групп работать не будут. Переезжаю на новый гораздо более мощный сервер. Создал реплику mongodb, но при нагрузке реплика не успевает догнать мастер-ноду. Если к вечеру всё применится, будут временные отключения бота.
Сегодня я официально старый 😢 Подписка на Telesint - лучший подарок ❤️
Showing the 12 most recent of 21 posts we hold for @telesint. 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.
Posts edited after publishing
@telesint edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 October 2026
- Most recent edit
- 8 October 2026
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 20 October 2026 — this entry's latest reading, not the date you are reading this.
“Ход разработки Аналитика Telegram” (@telesint), 27,415 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/telesint.
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.