Telegram RegisterThe public register of Telegram
Telegram profile photo for TON CIS LIVE

Channel

TON CIS LIVE

@toncislive

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003461037842
TypeChannel
Username@toncislive
Created13 November 2025measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live13 September 2026
Measurements held2
On Telegramt.me/toncislive

Growth

27 August 2026 — 2 subscribers14 August 2026 — 2 subscribers7 August 202614 August 2026
2 measurements spanning 7 days. 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–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 06:042no change
7 Aug 2026, 17:382first reading

Engagement

12 posts held, back to 13 November 2025the 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 12 posts for this entry, the most recent from 15 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
11

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

15 Nov 2025, 16:07 UTC19 viewsread 14 August 2026

⚡️Telegram запустил тест аукционов подарков: в течение 50 раундов будут разыграны 20 эксклюзивных Telegram Plane за раунд — первый длится час, остальные по 5 минут. — @toncislive

15 Nov 2025, 15:03 UTC20 viewsread 14 August 2026

⚡️TON CIS Hub объявил митап для билдеров в Тбилиси — 22 ноября пройдёт офлайн-встреча с поддержкой проектов, разбором вертикалей и нетворкингом для разработчиков экосистемы. — @toncislive

14 Nov 2025, 22:55 UTC20 viewsread 14 August 2026

⚡️Telegram 12.2 получил крупное ноябрьское обновление: прямые эфиры в историях, регулярные сообщения, аукционы подарков и новый Liquid Glass-редизайн на Android. — @toncislive

14 Nov 2025, 13:49 UTC20 viewsread 14 August 2026

⚡️TON CIS Hub открыл подачу на Builders Call — приватный созвон 21 ноября, где проекты региона получат фидбек от команды TON и найдут новые точки роста. — @toncislive

14 Nov 2025, 09:23 UTC21 viewsread 14 August 2026

⚡️Tolk v1.2 вышел с TVM 12 — единый внутренний address, rich bounces с полным телом, дешёвый builder-to-slice, лямбды и улучшенный компилятор. — @toncislive

13 Nov 2025, 20:26 UTC22 viewsread 14 August 2026

⚡️Telegram Beta 12.2.0 (6287) для Android исправили баги лайв историй — PiP, глитчи при открытии клавиатуры, скрытую кнопку поиска эмодзи и автоскролл в чате лайв-сториз. — @toncislive

13 Nov 2025, 20:22 UTC21 viewsread 14 August 2026

⚡️Telegram расширил Gift Auction: индикатор активных аукционов, повышение ставок, уведомления о перебитых биддах, история выигранных подарков и полный возврат Stars за проигравшие ставки. — @toncislive

13 Nov 2025, 18:08 UTC20 viewsread 14 August 2026

⚡️В Telegram Beta 12.2.0 для Android появилась аукционная покупка подарков — теперь отображается ссылка на аукцион, использующая серверное поле title. — @toncislive

13 Nov 2025, 17:01 UTC19 viewsread 14 August 2026

⚡️TON утвердил стандарт TEP-526 — единый формат отображения балансов токенов, позволяющий поддерживать ребейсинг, начисление доходности и другие продвинутые механики без потери точности. — @toncislive

13 Nov 2025, 16:48 UTC19 viewsread 14 August 2026

⚡️Французские следователи полностью сняли ограничения с Павла Дурова: отменён запрет на выезд и требование отмечаться в полиции. — @toncislive

13 Nov 2025, 16:43 UTC19 viewsread 14 August 2026

⚡️TON CIS Hub опубликовал большую подборку из 14 записей воркшопов — смарт-контракты, Tolk, DeFi, GameFi и Telegram In-App Assets в одном посте. — @toncislive

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

Mentions

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.

“TON CIS LIVE” (@toncislive), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/toncislive.

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.