Telegram RegisterThe public register of Telegram
Telegram profile photo for Центр CIGR

Channel

Центр CIGR

@CenterCIGR

On this record: Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

384subscribers

-1 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-1001393550389
TypeChannel
Username@CenterCIGR
Created16 February 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/CenterCIGR

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

384385384.56 August 2026 — 385 subscribers6 August 2026 — 385 subscribers18 August 2026 — 384 subscribers26 August 2026 — 385 subscribers9 September 2026 — 384 subscribers6 August 20269 September 2026
5 measurements spanning 35 days, net -1. 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 384–385 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 23:37384-1
26 Aug 2026, 05:13385+1
18 Aug 2026, 23:48384-1
6 Aug 2026, 20:17385no change
6 Aug 2026, 06:39385first reading

Engagement

9 posts held, back to 6 August 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 06:38 UTC4 viewsread 6 August 2026
Forwarded from @belarusian_silovikVideo

Момент атаки судна у берегов Одессы. БС в TG ✊ | БС в МАХ 🤫

6 Aug 2026, 06:15 UTC6 viewsread 6 August 2026
Forwarded from @WarDonbass

❗️В Ярославской области отразили самую массовую атаку БПЛА, сообщил губернатор региона Михаил Евраев. Силами РЭБ и ПВО ликвидированы 92 БПЛА. Сгорел частный дом, в нескольких многоквартирных домах выбиты стекла, есть повреждения автомобилей. Жертв и пострадавших нет.

6 Aug 2026, 04:44 UTC6 viewsread 6 August 2026
Forwarded from @warhistoryalconafterPhoto

🇺🇦🇷🇺 Ущерб от действий украинских боевиков в Курской области превысил 504 миллиарда рублей, сообщили в СК. Другие заявления официального представителя ведомства Светланы Петренко: ▪️Жертвами вторжения ВСУ в Курскую область стали 640 мирных жителей. ▪️Следователи зафиксировали преступления украинских боевиков в отношении мирного населения более чем в 25 населённых пунктах региона, всего возбуждено 711 уголовных дел

6 Aug 2026, 03:57 UTC4 viewsread 6 August 2026
Forwarded from @creamy_capricePhoto

05.08.26 Констатиновка - Красный Кут - Приют - Торское Позиционные боевые действия в районе Красноармейска. ВС РФ продвинулись на 1 км около Константиновки и удерживают передовые позиции в населённых пунктах Приют, Торское и на южных подступах к Красному Куту. 0:23 48.55350,37.40402 На карте 0:46 48.54001,37.40825 На карте 2:17 48.55050,37.42238 На карте Источник 21+ Геопривязка #ru

6 Aug 2026, 03:45 UTC2 viewsread 6 August 2026
Forwarded from @olgavyazovskaya2014Photo

‼️Большой сбор помощи для детей Донбасса и в зоне СВО! С 2014 года Ольга Вязовская помогает детям-сиротам, детям инвалидам и многодетным семьям в зоне боевых действий, в наиболее тяжелых районах Донбасса и СВО. На фото(из наших отчетов) детки, эвакуированные из района боевых действий, жилье было разрушено укронацистами. На фото 1 девочка инвалид Надежда. Почти не видит и не слышит. За последнюю неделю помогли бол

6 Aug 2026, 03:44 UTC4 viewsread 6 August 2026
Forwarded from @rybarPhoto

📝Хроника специальной военной операции📝 За 5 августа 2026 года 🧨Российские войска в ночь на 5 августа нанесли серию ударов по логистическим объектам противника в Киевской и Днепропетровской областях. Под ударами вновь оказались мощности «Новой почты», а склады Novus и «Терминал Розетка» и вовсе были почти полностью уничтожены. Помимо этого атака пришлась на мощности производственной площадки Epicentr Ceramic Corpora

6 Aug 2026, 03:43 UTC4 viewsread 6 August 2026
Forwarded from @dva_majors

#Сводка на утро 6 августа 2026 года ▪️В Ярославле после налета перекрыто движение по Московскому проспекту, изменена работа общественного транспорта. Судя по записям с каналов противника, его целью снова был Ярославский НПЗ. Сбиты БПЛА, шедшие на Москву, отражение налета шло в Севастополе и Крыму. За световой день до 20.00 сбиты 200 дронов, сообщило оборонное ведомство. ▪️ВС России продолжили удары по объектам мо

6 Aug 2026, 03:42 UTC4 viewsread 6 August 2026
Forwarded from @warriorofnorthPhoto

5 августа группировка войск "Север" продолжила создание полосы безопасности в Харьковской и Сумской областях #Группировка_войск_Север В Черниговской области в районе села Бутовка (Сосницкий район) нападению со стороны местных жителей подверглась группа украинских пограничников, которые ошибочно были приняты за сотрудников ТЦК. В результате конфликта один из пограничников был убит. На Сумском направлении Штурмовик

6 Aug 2026, 02:43 UTC5 viewsread 6 August 2026
Forwarded from @voin_dvVideo

📡 Очередная ликвидированная группа противника на Запорожском направлении. Работа операторов БпЛА 35 гвардейского полка РХБЗ 35 армии группировки войск "Восток". @voin_dv | @voin_dv в MAX

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

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.

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.

Телеблог Ростов Таганрог Шахты Волгодонск Новочеркасск Батайск Новошахтинск Азов Реклама Афиша Объявления Аренда квартиры
@Volgodonsk_Novocherkassk24 · 89,877
Telegram ranks this channel #57 of 83 here — alongside 82 others — read 9 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Центр CIGR” (@CenterCIGR), 384 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/CenterCIGR.

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.