📍Зірка ( Донецька область) 🇺🇦СОУ форсували річку та звільнили населений пункт під питанням н.п Ялта можливо сіра зона звільнено ≈3,99 км² 🤩finsmap
❤15🔥5custom 54047444410742943861

Channel
@finsmap
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
702subscribers
+47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002560022506 |
|---|---|
| Type | Channel |
| Username | @finsmap |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/finsmap |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 04:18 | 702 | +10 |
| 3 Sept 2026, 01:15 | 692 | -2 |
| 27 Aug 2026, 21:56 | 694 | -2 |
| 21 Aug 2026, 18:25 | 696 | +29 |
| 14 Aug 2026, 23:38 | 667 | +12 |
| 8 Aug 2026, 02:45 | 655 | no change |
| 7 Aug 2026, 17:09 | 655 | first reading |
17 posts held, back to 22 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 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 17 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
372 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 153 | 41.1% | |
| 🔥 | 93 | 25.0% | |
| 🤬 | 43 | 11.6% | |
| custom 5404744441074294386 | 24 | 6.45% | |
| custom 5402385129639256730 | 18 | 4.84% | |
| 😢 | 18 | 4.84% | |
| custom 5190867898800821266 | 11 | 2.96% | |
| custom 5404327206476326350 | 9 | 2.42% | |
| custom 5406872902312141263 | 3 | 0.806% |
Custom emoji. 5 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 16 of the 17 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 372 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 22 July 2026 to 7 August 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.
📍Зірка ( Донецька область) 🇺🇦СОУ форсували річку та звільнили населений пункт під питанням н.п Ялта можливо сіра зона звільнено ≈3,99 км² 🤩finsmap
❤15🔥5custom 54047444410742943861
△Fins | карта війни△ pinned «✍️дорогі друзі Адмін поїхав на БЗВП,якщо буде можливість викладати карту буду по максимуму використовувати цю можливість всіх обійняв💖»
📍Поддубне - Мирне - Воскресенка 🇺🇦СОУ продовжують контрнаступальні дії в донецькій області зрозуміти це можна по супутникових знімках які демонструють удари російських авіабомб (КАБ/ФАБ) по передовим позиціях ЗСУ просування СОУ ≈19,7 км² 🤩finsmap
❤26custom 54047444410742943865custom 51908678988008212664
📍Рай-Олександріївка 🇷🇺Бійці ЗСрф закріпилися на схід від н.п просування ворога ≈15,0 км² 🤩finsmap
😢16
🚽маємо гарні новини з донецької області
custom 540238512963925673015🔥1
📍Оріхів 🇺🇦СОУ звільнили лісосмуги на південь від міста звільнено ≈4,82 км² 🤩finsmap
🔥20
📍Мілове 🇺🇦СОУ провели атаку зі застосуванням танків,один з них було знищено але до цього танк подолав територію яка вважалася під контролем ворога звільнено ≈1,55 км² 🤩finsmap
🔥19custom 54047444410742943864custom 54043272064763263501
✍️дорогі друзі Адмін поїхав на БЗВП,якщо буде можливість викладати карту буду по максимуму використовувати цю можливість всіх обійняв💖
❤33custom 54047444410742943866😢2
📍Констянтинівка 🇺🇦СОУ відновили позиції по вул. Героїв праці та вул. Херсонській 🇷🇺групи ворога інфільтруются в напрямку н.п Алексеево-Дружковка загалом 70% міста це сіра зона 🤩finsmap
❤24custom 54023851296392567303custom 54047444410742943862
📍Козачья Лопань 🇺🇦СОУ звільнили населений пункт від ворога звільнено ≈11,7 км² 🤩finsmap
❤29custom 51908678988008212664custom 54068729023121412633
📍Миколаївка ( Словʼянський напрямок ) групи ворога досягли дач та вул. Ювілейної 🤩finsmap
🤬16custom 54043272064763263503
📍Білецьке Штурмові групи ЗСрф захопили всю східну частину залізничних колій та лісосмуги біля н.п Сухецьке,Затишок,Никаровка в самому ж місті продовжуються бої за центральну частину просування ЗСрф ≈12,9 км² 🤩finsmap
🤬14custom 54043272064763263501
Showing the 12 most recent of 17 posts we hold for @finsmap. 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 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.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“△Fins | карта війни△” (@finsmap), 702 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/finsmap.
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.