Telegram RegisterThe public register of Telegram
Telegram profile photo for Карта СВО. Главное

Channel

Карта СВО. Главное

@svomapp

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Cite this entry

10,172subscribers

+233 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001971509228
TypeChannel
Username@svomapp
DescriptionИнтерактивная карта Спецоперации https://svomapp.ru/ Прислать информацию или задать вопрос (анонимно): @svomapp_support_bot
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/svomapp

Topic

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 67% 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.

Growth

9,93710,19510,0667 August 2026 — 9,939 subscribers8 August 2026 — 9,937 subscribers11 August 2026 — 9,946 subscribers14 August 2026 — 9,974 subscribers17 August 2026 — 10,035 subscribers18 August 2026 — 10,053 subscribers19 August 2026 — 10,068 subscribers20 August 2026 — 10,058 subscribers22 August 2026 — 10,108 subscribers24 August 2026 — 10,121 subscribers25 August 2026 — 10,129 subscribers26 August 2026 — 10,132 subscribers27 August 2026 — 10,137 subscribers28 August 2026 — 10,145 subscribers29 August 2026 — 10,152 subscribers30 August 2026 — 10,150 subscribers31 August 2026 — 10,142 subscribers1 September 2026 — 10,123 subscribers2 September 2026 — 10,117 subscribers3 September 2026 — 10,120 subscribers6 September 2026 — 10,132 subscribers9 September 2026 — 10,144 subscribers11 September 2026 — 10,153 subscribers13 September 2026 — 10,158 subscribers15 September 2026 — 10,155 subscribers17 September 2026 — 10,152 subscribers26 September 2026 — 10,144 subscribers4 October 2026 — 10,187 subscribers8 October 2026 — 10,175 subscribers13 October 2026 — 10,174 subscribers14 October 2026 — 10,179 subscribers15 October 2026 — 10,177 subscribers16 October 2026 — 10,176 subscribers18 October 2026 — 10,182 subscribers19 October 2026 — 10,180 subscribers20 October 2026 — 10,185 subscribers21 October 2026 — 10,189 subscribers22 October 2026 — 10,188 subscribers24 October 2026 — 10,195 subscribers25 October 2026 — 10,183 subscribers26 October 2026 — 10,175 subscribers27 October 2026 — 10,174 subscribers29 October 2026 — 10,172 subscribers30 October 2026 — 10,167 subscribers31 October 2026 — 10,177 subscribers1 November 2026 — 10,167 subscribers2 November 2026 — 10,161 subscribers3 November 2026 — 10,157 subscribers4 November 2026 — 10,168 subscribers5 November 2026 — 10,165 subscribers6 November 2026 — 10,183 subscribers7 November 2026 — 10,176 subscribers8 November 2026 — 10,177 subscribers10 November 2026 — 10,172 subscribers10,1727 August 202610 November 2026
54 measurements spanning 95 days, net +233. 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 9,898–10,234 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
10 Nov 2026, 03:1510,172-5
8 Nov 2026, 20:2610,177+1
7 Nov 2026, 13:4810,176-7
6 Nov 2026, 13:3610,183+18
5 Nov 2026, 15:0910,165-3
4 Nov 2026, 16:1810,168+11
3 Nov 2026, 16:3910,157-4
2 Nov 2026, 14:1610,161-6
1 Nov 2026, 17:2010,167-10
31 Oct 2026, 14:5910,177+10
30 Oct 2026, 14:2710,167-5
29 Oct 2026, 16:4610,172-2
27 Oct 2026, 14:3910,174-1
26 Oct 2026, 15:5710,175-8
25 Oct 2026, 16:5610,183-12
24 Oct 2026, 14:4810,195+7
22 Oct 2026, 14:2110,188-1
21 Oct 2026, 08:4910,189+4
20 Oct 2026, 08:3110,185+5
19 Oct 2026, 08:4710,180first reading

Engagement

199 posts held, back to 6 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 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.9%
avg views ÷ 10,172 subscribers
Avg views / post
1,410
47 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
47
of 199 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held199 (6 August 2026 – 11 November 2026)
Views total66,287
Reactions total1,043
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 10:41 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

Photos
≈2,850
Videos
≈1,780
Links
≈3,630

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
1h 29m
Average length
1m 13s

Measured directly from 74 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.

Reaction mix

4,812 reactions across 199 posts, in 20 distinct kinds. The most used accounts for 26.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52021656041145195601,27026.4%
👍1,01721.1%
🔥55011.4%
🕊49310.2%
❤48310.0%
🤬3487.23%
🤡1733.60%
😁1102.29%
💩791.64%
👏631.31%
🙏631.31%
🤔621.29%
👎290.603%
🖕220.457%
💯110.229%
😡110.229%
custom 519956880246284652580.166%
💊80.166%
🫡70.145%
😢50.104%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 199 of the 199 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 4,812 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 199 most recent posts we hold, published 6 August 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 Stars

Stars received
1
across the posts below
Posts paid on
1
of 199 we hold a reading for · 0.5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @svomapp. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 199 most recent posts we hold for this entry, published 6 August 2026 to 11 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Advertising

Ad load
0.503%
1 of 199 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
798
over 1 measured post
Median views · rest
1,260
over 198 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFHNh3AZ120 August 202620 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 199 most recent posts we hold, published 6 August 2026 to 11 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 47 posts held from the last 30 days (0%) 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).

11 Nov 2026, 09:48 UTC324 views11 reactionsread 11 November 2026
Photo

Войска РФ освободили Воскресенку в Запорожской области 🗺 Карта 📌 Канал в MAX

custom 52021656041145195608🔥3

11 Nov 2026, 09:48 UTC327 views11 reactionsread 11 November 2026
Photo

Минобороны РФ сообщило, что российские войска взяли под контроль Шиловку в Донецкой Народной Республике. 🗺 Карта 📌 Канал в MAX

🔥5custom 52021656041145195604❤2

11 Nov 2026, 06:50 UTC586 views14 reactionsread 11 November 2026

Два мирных жителя погибли в результате ночной атаки украинских беспилотников на Смоленскую область. Обломки дрона попали в многоэтажный жилой дом в городе Ярцево, что привело к пожару. Из зоны возгорания были спасены десять человек. Всего за ночь силы ПВО уничтожили 37 украинских БПЛА над территорией региона. 🗺 Карта 📌 Канал в MAX

🤬10🕊4

10 Nov 2026, 11:45 UTC≈1,060 views20 reactionsread 11 November 2026
Photo

Российские войска нанесли удары по электроподстанциям в Вольногорске Днепропетровской области и Кременчуге Полтавской области. 🗺 Карта 📌 Канал в MAX

🕊8🔥5👍4custom 52021656041145195603

10 Nov 2026, 10:38 UTC≈1,090 views28 reactionsread 11 November 2026
Photo

Украина теряет в среднем больше 500 кв км территории в месяц. Любопытная география переговоров: между Женевой и Абу-Даби по прямой – 5 000 км. Столько же квадратных километров освободили российские войска с прошлого женевского раунда 17–18 февраля. А это, между прочим, больше 250 населённых пунктов. 🗺 Карта 📌 Канал в MAX

❤11custom 52021656041145195609🕊3🔥2👍1💊1🤡1

10 Nov 2026, 10:08 UTC≈1,010 views21 reactionsread 11 November 2026
Photo

Вооруженные силы РФ сообщили о поражении двух сухогрузов и танкера с горючим для украинской армии. Инцидент произошел в акватории Черного моря, северо-восточнее и восточнее Одессы. 🗺 Карта 📌 Канал в MAX

🔥16custom 52021656041145195603🕊2

10 Nov 2026, 09:21 UTC≈1,040 views30 reactionsread 11 November 2026
Photo

Минобороны РФ сообщило, что российские войска освободили населенный пункт Никольское в Сумской области. 🗺 Карта 📌 Канал в MAX

custom 520216560411451956022👍4🕊3❤1

10 Nov 2026, 06:05 UTC≈1,100 views20 reactionsread 11 November 2026
Photo

Переговоры российской и украинской делегаций начнутся сегодня в 10:50 по московскому времени 🗺 Карта 📌 Канал в MAX

🤔13👍3🕊3🙏1

9 Nov 2026, 20:01 UTC≈1,180 views24 reactionsread 11 November 2026
Photo

В Одессе беспилотниками поражен логистический центр "Сухой порт", который использовался для нужд ВСУ. Также ударом затронут сухогруз в акватории Черного моря к юго-западу от города. 🗺 Карта 📌 Канал в MAX

🔥16custom 52021656041145195606🕊2

9 Nov 2026, 17:17 UTC≈1,240 views13 reactionsread 11 November 2026
Video

Секретный ответ биолабораториям: первые испытания автономного тактического овоща Пока противник ждёт ПВО, отечественные нейросети выкатили асимметричный ответ. В сети появились секретные кадры разработки краснодарских селекционеров – разумный тактический огурец «Дон Ку-Ку». ТТХ: длина 13 см, повышенная живучесть, полностью автономен, устойчив к РЭБ, напрочь лишён страха перед салатом. Минута военного сарказма посред…

😁8❤2🕊2👍1

9 Nov 2026, 10:56 UTC≈1,240 views31 reactionsread 11 November 2026
Photo

Российские войска поразили две электроподстанции. Удары пришлись по объектам в Кривом Роге и Черкассах. 🗺 Карта 📌 Канал в MAX

custom 520216560411451956018👍5🔥5🕊2❤1

9 Nov 2026, 10:35 UTC≈1,260 views31 reactionsread 11 November 2026
Photo

Российские войска ночью нанесли удар по электроподстанции в Белой Церкви Киевской области. Она обеспечивала работу предприятий ВПК Украины. 🗺 Карта 📌 Канал в MAX

custom 520216560411451956016👍7🔥6🕊2

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

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Карта СВО. Главное” (@svomapp), 10,172 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/svomapp.

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.