📌 ВСУ восстановили контроль над селом Ямполь • На видео ВС РФ наносят удары по пунктам управления БПЛА ВСУ Площадь продвижения: 3,6 км² 📌 GeoTope | 📍Карта
👍12❤🔥8👎5custom 52426778272994503405😁3

Channel
@GeoTope
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
535subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002232695332 |
|---|---|
| Type | Channel |
| Username | @GeoTope |
| Description | Новости и обстановка на фронте — на моем канале с картой. Мы стремимся к объективности и доносим до аудитории только проверенную информацию. |
| 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 | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/GeoTope |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:49 | 535 | no change |
| 7 Aug 2026, 13:41 | 535 | first reading |
12 posts held, back to 13 October 2025 — 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 pageof 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 12 posts for this entry, the most recent from 1 November 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 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 7 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.
230 reactions across 12 posts, in 17 distinct kinds. The most used accounts for 35.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 81 | 35.2% | |
| 🖕 | 30 | 13.0% | |
| 🤬 | 19 | 8.26% | |
| ❤🔥 | 16 | 6.96% | |
| 👎 | 16 | 6.96% | |
| 🔥 | 16 | 6.96% | |
| ❤ | 12 | 5.22% | |
| custom 5242677827299450340 | 10 | 4.35% | |
| 🤯 | 10 | 4.35% | |
| 🥰 | 6 | 2.61% | |
| 😁 | 4 | 1.74% | |
| ☃ | 2 | 0.87% | |
| 👀 | 2 | 0.87% | |
| 💊 | 2 | 0.87% | |
| 😡 | 2 | 0.87% | |
| ⚡ | 1 | 0.435% | |
| 🤔 | 1 | 0.435% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 12 of the 12 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 230reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 13 October 2025 to 1 November 2025, 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,6 км² 📌 GeoTope | 📍Карта
👍12❤🔥8👎5custom 52426778272994503405😁3
Что вы все так взволновались, меня пару дней не было
🖕16custom 52426778272994503403☃2
📌 Ситуация на Покровском направлении Подразделения ВС РФ начали штурм Покровска и приступили к продвижению по улицам города. Одновременно российские войска вошли в Мирноград, где пытаются закрепиться. • Покровск: Занята южная часть города, а также села Троянда и Чунишино. Ведутся попытки закрепиться в соседних населенных пунктах Рог и Гнатовка • Мирноград (юго-восток): Войска заняли села Балаган, Казацкое и Промин…
🤯8🔥5👀2custom 52426778272994503402❤1
📌 Коррекция линии фронта в Алексеевке • ВСУ нанесли удар авиабомбой AASM HAMMER по расположению российских военнослужащих и складу боеприпасов в Алексеевке 📌 GeoTope | 📍Карта
👍8🤬4❤1
📌 ВС РФ продвинулись в Полтавке • На видео ВСУ наносят удар по российской позиции Площадь продвижения: 0,4 км² 📌 GeoTope | 📍Карта
👍6🤬3🖕2❤1
📌 ВС РФ продвинулись северо-восточнее Ялты Площадь продвижения: 13,6 км² 📌 GeoTope | 📍Карта
👍8🖕5❤1
📌 Ситуация на Торецком направлении • ВСУ обстреливают российскую позицию на сельскохозяйственных строениях на территории Константиновки. Предтечино перенесено в серую зону • Также зафиксирован украинский военнослужащий на северо-западе Торецка. Добавлена серая зона 📌 GeoTope | 📍Карта
❤2🔥2🤯2👍1
📌 Сегодня утром ВС РФ предприняли механизированную атаку на Шахово и Софиевку • В штурме участвовал 1 танк и 13 бронетранспортеров с пехотой • В результате танк и 8 бронетранспортеров были уничтожены артиллерией и FPV-дронами 📌 GeoTope | 📍Карта
🔥9👍2😡2❤1
📌 ВС РФ заняли Алексеевку, а также ряд полей юго-восточнее села в Днепропетровской области • На кадре российские военнослужащие демонстрируют флаг РФ в селе Площадь продвижения: 44,9 км² 📌 GeoTope | 📍Карта
👍22👎11❤3⚡1🤬1
Прогноз от 110-й бригады ВСУ в Днепропетровской области: • Российские войска сконцентрировали ударную группировку (5-7 тысяч человек) для наступления в направлении Вишневое - Егоровка с целью форсирования реки Янчур и последующего продвижения на Покровское. • Российские войска наступают исключительно за счет значительного превосходства в живой силе, неся большие потери. Цель: Уничтожение логистических путей снабже…
🤬8🥰6❤2🤔1😁1
📌 ВСУ вернули южную часть Алексеевки Площадь продвижения: 1,2 км² 📌 GeoTope | 📍Карта
❤🔥8👍6💊2🖕2
📌 ВС РФ продвинулись западнее Котляровки Площадь продвижения: 1,5 км² 📌 GeoTope | 📍Карта
👍16🖕5🤬3
Showing the 12 most recent of 12 posts we hold for @GeoTope. 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“GeoTope” (@GeoTope), 535 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/GeoTope.
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.