Channel
@colonel_cassad_plus
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
348subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002199564303 |
|---|---|
| Type | Channel |
| Username | @colonel_cassad_plus |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/colonel_cassad_plus |
International news — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 42 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @boris_rozhin/2213218 Aug 2026, 03:03 UTC | @colonel_cassad_plus/47372 · this entry8 Aug 2026, 03:03 UTC | 1.00 | under a minute |
| @boris_rozhin/2211116 Aug 2026, 11:44 UTC | @colonel_cassad_plus/47377 · this entry8 Aug 2026, 04:33 UTC | 1.00 | 41 hours |
| @boris_rozhin/2213348 Aug 2026, 04:35 UTC | @colonel_cassad_plus/47378 · this entry8 Aug 2026, 04:35 UTC | 1.00 | under a minute |
| @boris_rozhin/2213388 Aug 2026, 05:10 UTC | @colonel_cassad_plus/47381 · this entry8 Aug 2026, 05:10 UTC | 1.00 | under a minute |
| @boris_rozhin/2213398 Aug 2026, 05:35 UTC | @colonel_cassad_plus/47382 · this entry8 Aug 2026, 05:35 UTC | 1.00 | under a minute |
| @boris_rozhin/2213418 Aug 2026, 05:47 UTC | @colonel_cassad_plus/47384 · this entry8 Aug 2026, 05:47 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @boris_rozhin | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @boris_rozhin (6–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 8 August 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 42 channels, the one whose matching posts we hold earliest is @opernn. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 42 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
1 more channel is in this same group but not listed individually here.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 07:26 | 348 | +2 |
| 29 Oct 2026, 14:00 | 346 | -2 |
| 23 Oct 2026, 01:48 | 348 | +6 |
| 16 Oct 2026, 19:59 | 342 | +2 |
| 10 Oct 2026, 02:39 | 340 | +2 |
| 30 Sept 2026, 03:16 | 338 | +2 |
| 31 Aug 2026, 05:28 | 336 | -3 |
| 23 Aug 2026, 10:48 | 339 | +2 |
| 15 Aug 2026, 04:25 | 337 | +1 |
| 8 Aug 2026, 07:04 | 336 | no change |
| 7 Aug 2026, 14:34 | 336 | first reading |
20 posts held, back to 8 August 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 videos 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.
Группировка войск "Север" освободила село Ивановка Харьковской области! Штурмовые подразделения 126 мсп 71 гв. мсд ГВ "Север" в ходе ожесточенных боев выбили националистов 159 омбр из села Ивановка Волчанского района и освободили населенный пункт. Накануне для удержания Ивановки противник пытался перебросить группу мотивированных националистов из числа инструкторов 159-й механизированной бригады. Передовая группа п…
Изменения на карте за прошедшие сутки: - освобождено Анищино (+8,6км2) - продвижение у Новоподгороднего (+4км2) - продвижение у Журавлёвки (+0,3км2) Карты: @divgen
В течение прошедшей ночи дежурными силами ПВО перехвачены и уничтожены 397 украинских беспилотных летательных аппаратов самолетного типа над территориями Белгородской, Брянской, Воронежской, Курской, Липецкой, Орловской, Пензенской, Ростовской, Рязанской, Самарской, Саратовской, Тамбовской, Тульской областей, Краснодарского края, Республики Крым и акваторией Азовского моря. - Одно из промышленных предприятий Самарск…
Ещё ночные прилеты по Киеву прилетело 8 баллистических ракет.
Сержант Вадим Ахмедов родом из Дербента. Он награжден Георгиевским крестом IV степени за спасение боевых товарищей. Это было 2024 году в Херсонской области. Вадим дежурил на наблюдательном посту. Через несколько минут после проезда автомобиля с военнослужащими он услышал громкий взрыв и сразу понял: надо спешить на помощь. В этот день ему пришлось организовывать эвакуацию сразу троих военнослужащих, получивших ранен…
Севастополь ✅✅✅ Отбой воздушной тревоги
Российские военные сорвали попытку ВСУ форсировать Днепр со стороны Ингульца, сообщил ТАСС командир роты с позывным Калибр. Видео: Даниил Михайлов/Минобороны России/ТАСС
В Севастополе военные продолжают отражать атаку ВСУ, работает ПВО и мобильные огневые группы. Сбито 12 БПЛА в районе Северной стороны, Балаклавском и Гагаринском районах. Не пренебрегайте мерами безопасности! ⚡️⚡️⚡️⚡️Покиньте открытые пространства и оставайтесь в безопасных местах. Наши военные ведут работу по уничтожению вражеских БПЛА из различных средств поражения, в том числе и из стрелкового оружия. Берегит…
"Бастионы" взяли на прицел корабли условного противника. На побережье Калининградской области расчеты ракетных комплексов разыграли сценарий отражения угрозы с моря. Военные обнаружили надводные цели, отработали нанесение удара и сразу после "пуска" сменили позиции. На это ушли считанные минуты. В учениях задействовали около 100 военнослужащих и более 10 единиц техники.
Схема ночных ударов по Киеву по версии противника. Прилетало само собой не только в Киеве, но с недавних пор на таких схемах противник принципиально игнорирует массированные удары по инфраструктуре в других областях. Ночью были также прилеты в Кременчуге, Полтавской, Днепропетровской, Сумской областях, а также в Николаеве. И т.д.
Сегодня ночью Вооруженными Силами Российской Федерации нанесен групповой удар высокоточным оружием наземного базирования по предприятию военной промышленности и складу горюче-смазочных материалов в городе Киеве. Поражены в городе Киеве: - промышленное предприятие Киев-111 (ООО «Файер Пойнт»), производящее комплектующие и боевые части для крылатых ракет наземного базирования FP-5 «Фламинго». На объекте также хранятс…
На территории предприятия в Киеве вспыхнул пожар в результате ночных ударов, сообщили в местных экстренных службах.
Showing the 12 most recent of 20 posts we hold for @colonel_cassad_plus. 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.
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.
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.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“ColonelCassad” (@colonel_cassad_plus), 348 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/colonel_cassad_plus.
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.