Channel
@kapticxem
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
8,846subscribers
-102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002397567235 |
|---|---|
| Type | Channel |
| Username | @kapticxem |
| Description | Война на Украине |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/kapticxem |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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. 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.
No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Lisichanskinfo | 12 (8/8 hand-verifiable sample passed) | 0.99 | 21 minutes | this entry (12–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 150 comparable posts for this entry, running 30 July 2026 to 11 November 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.
Recorded under the key clone_source, last confirmed 12 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 02:28 | 8,846 | +1 |
| 5 Nov 2026, 20:45 | 8,845 | -4 |
| 3 Nov 2026, 04:28 | 8,849 | -2 |
| 31 Oct 2026, 07:46 | 8,851 | -10 |
| 28 Oct 2026, 07:50 | 8,861 | -4 |
| 25 Oct 2026, 00:45 | 8,865 | -7 |
| 22 Oct 2026, 07:28 | 8,872 | -5 |
| 19 Oct 2026, 02:37 | 8,877 | -21 |
| 15 Oct 2026, 19:30 | 8,898 | +8 |
| 12 Oct 2026, 17:30 | 8,890 | -5 |
| 6 Oct 2026, 04:00 | 8,895 | +1 |
| 28 Sept 2026, 23:41 | 8,894 | -1 |
| 19 Sept 2026, 09:22 | 8,895 | -12 |
| 15 Sept 2026, 06:16 | 8,907 | -2 |
| 11 Sept 2026, 14:17 | 8,909 | -6 |
| 7 Sept 2026, 08:57 | 8,915 | -8 |
| 2 Sept 2026, 04:58 | 8,923 | -8 |
| 30 Aug 2026, 09:03 | 8,931 | +20 |
| 27 Aug 2026, 02:32 | 8,911 | -8 |
| 23 Aug 2026, 16:13 | 8,919 | first reading |
171 posts held, back to 30 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 49 pages of Telegram’s post history, 20 posts per page.
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 11 November 2026 |
|---|---|
| Posts held | 171 (30 July 2026 – 11 November 2026) |
| Views total | 220,220 |
| Reactions total | 5,603 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 00:44 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.
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 52 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.
15,644 reactions across 163 posts, in 56 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4,989 | 31.9% | |
| 🔥 | 3,959 | 25.3% | |
| 😁 | 1,817 | 11.6% | |
| ❤ | 1,033 | 6.60% | |
| 💯 | 939 | 6.00% | |
| 👏 | 693 | 4.43% | |
| 🙏 | 672 | 4.30% | |
| 🤣 | 440 | 2.81% | |
| 🤔 | 201 | 1.28% | |
| 🤬 | 174 | 1.11% | |
| 🤡 | 132 | 0.844% | |
| 👌 | 66 | 0.422% | |
| 👀 | 46 | 0.294% | |
| 🤷♂ | 45 | 0.288% | |
| ❤🔥 | 39 | 0.249% | |
| 👎 | 34 | 0.217% | |
| 🏆 | 28 | 0.179% | |
| 🥰 | 25 | 0.16% | |
| ☃ | 24 | 0.153% | |
| 🫡 | 23 | 0.147% | |
| 36 further kinds | 265 | 1.69% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 168 of the 171 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 16,128 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 171 most recent posts we hold, published 30 July 2026 to 11 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram’s own ‘edited’ marker: 19 of 68 posts held from the last 30 days (27.9%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Зеля прилетел в Ирландию на какой то очередной европейский местячковый шабаш. Мероприятие двухдневное. То есть ненька увидит своего фюрера, в лучшем случае, только послезавтра. Куда он намылится после Дублина пока неизвестно, но время полистать интернет и выбрать очередную европейскую тусовку у него еще будет. схемы и карты в Максе
😁27💯11❤1🤡1
Вы наверное уже слышали новость-предположение, что Зеленский начинает бояться находиться на Украине, у него развивается какая то разновидность паранойи. И вот он уже завис на пару дней в Дании, встречаясь там со всеми подряд, а вот оттуда планирует улететь, нет не домой в Киев, а в Ирландию, где перехватит американских переговорщиков. Совсем не торопится. схемы и карты
😁57🤡10❤2😱2👍1💯1
И еще одно удачное попадание. В Черноморске (Одесская область) двумя КАБ поразили здание СБУ, взрывной волной досталось "Утреннему рынку" схемы и карты в Максе
🔥39👏13👍4❤1
Киевгорсвет сообщил о полном отключении уличного освещения. Водителей просят быть внимательными на дорогах, а пешеходов – использовать светоотражающие элементы и фонарики в темное время суток. Правильно, не хрен шастать по ночам. Сидите дома и ждите когда электричество появится в розетке. Факел и масляные лампы можно попробовать.
👍43👏10😁4❤3
"Дальневосточный экспресс", похоже, приготовил хохлам какую то лютую гадость-))))
🔥55🤔13👍6😁5
Группировка "Север" вчера забрала у хохлов Никольское. Таким образом, Могрица уходит в опорный хаб, а рубеж Марьино-Никольское-Бариловка рассекает большой лесной массив пополам, закрывая маршрут противнику через Никольское (черные пунктиры). Схема из статьи от 29 октября. схемы и карты в Максе
🙏51👏12🔥9❤2🏆2🤡1
Сегодня ночью массированно (около 20 штук) прилетело Геранями-2 по подстанциям Кривого Рога: Горная 330, Южная 330 и другим попроще-)). В городе наблюдались перебои с электричеством. Схемы и карты в Макс
👍49🔥20❤7👌2👏1
Поляки пытаются выцыганить у хохлов доступ к украинским беспилотным и антидроновым технологиям. Взамен обещают бесплатно отдать устаревшие самолёты МиГ-29. Всё бы ничего, но смущает цифра летаков-ДВА штуки. Я не пойму, кто там кого пытается наи..обмануть. Переговоры идут уже почти год. Игра была равна-играли два говна-))
😁65🤣15💯2
В Киеве сложная транспортная обстановка в связи с ударами по мостам. Команды Кличко и Зеленского продолжают обмениваться беспокоящими ударами. Зеля провел два правых боковых в голову и корпус: поручил премьер- министру представить программу бесплатного проезда в столице и найти резерв автобусов. Всё за счёт города, денег на это Европа, естественно, не выделит. Кличко ответил любимым двойным джебом в голову, держа пр…
😁77👍6🔥3❤2
https://sponsr.ru/cxemokart/193113/Vokrug_Drujkovki_nabludautsya_interesnye_sobytiya/ Пока команда Драпатого рисует цифры потерь в виртуале, на земле вокруг той же Дружковки сгущаются не тучи, а тучища и восточную часть города он уже практически не контролирует. Открываю очередной новый цикл статей - про Дружковку.
👏37🙏25👍14🫡4🔥3🤡1
К завтрашним переговорам сегодня в сводке клоуны из хохлоШтаба рывком увеличили наши потери еще на +600-))) схемы и карты
😁27🤷♂15👨💻7❤3
Россия применила климатическое оружие. Холодный фронт из Сибири коварно обогнул центрально-европейсую часть России и вторгся на территорию Западной Украины, где сегодня ночью температура опустится до минус 4. Холод, сука холод....-))) схемы и карты
😁91☃21❤9🔥3
Showing the 12 most recent of 171 posts we hold for @kapticxem. 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.
@kapticxem 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.
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 3 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Схемы и карты военных действий” (@kapticxem), 8,846 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/kapticxem.
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.