Channel
@andreevkamapping
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
236subscribers
+97 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003948585430 |
|---|---|
| Type | Channel |
| Username | @andreevkamapping |
| Created | Between 1 April 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/andreevkamapping |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 08:22 | 236 | +8 |
| 31 Aug 2026, 14:04 | 228 | +26 |
| 24 Aug 2026, 06:38 | 202 | +61 |
| 16 Aug 2026, 14:06 | 141 | +2 |
| 15 Aug 2026, 18:15 | 139 | first reading |
7 posts held, back to 14 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 7 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
29 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 44.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 13 | 44.8% | |
| 🔥 | 5 | 17.2% | |
| 🖕 | 4 | 13.8% | |
| 😡 | 4 | 13.8% | |
| ❤ | 2 | 6.90% | |
| 👎 | 1 | 3.45% |
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 6 of the 7 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 29 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 14 August 2026 to 14 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.
🚨GEOLOCATION CLARIFICATION 🚨 A geolocation was posted showing a Russian strike on the settlement of Dobropolye. Copernicus satellite data dates the strike to be around march-april~, as greenery begins to grow during the start and continuation of summer. The geolocator never claimed that it was modern, so its more of a correction of the situation for those using UAControlMap. On the left is April and on the right is …
👍4
✅ Correctly geolocated and correctly dated 🟡 Correctly geolocated but date is incorrect but close ❌ Either wrong place, wrong date, or old footage
🚨ENTIRE VOINDV GEOLOCATION CLARIFICATION 🚨 After looking through every single flag raise and painstakingly reviewing every single geolocation of the Russian flags posted by VoinDV. To review each flag I used Copernicus satellite data and compared it to the vegetation shown in the video. At least 6 of the 21 geolocations are either in the wrong place, dated wrong by a few months, or just rehashed old footage. The geo…
🔥5❤2👍1👎1
🚨GEOLOCATION CLARIFICATION 🚨 Geolocation of Russians in the settlement of Novoheorhiivka is correct but its atleast before July~ On the left is August 13th, the right is July 1st. 2:24 in the attached video: https://t.me/voin_dv/20675
👍3
🚨GEOLOCATION CLARIFICATION 🚨 Yet another geolocation that is dated to be way older. VoinDV showed a video of Russian soldiers apparently on the outskirts of Velykomykhailivka itself, the only problem is that when viewed on the date they claim it to be, the field shown is super black. Yet another date that is wrong, its most likely either ai or an old unpublished video of Russian infiltrators in the forests west of N…
😡4
🚨GEOLOCATION CLARIFICATION 🚨 Recently VoinDV came out to "respond" to the Ukrainian flags amid the Komar direction. In doing so they used months old footage dating back all the way to August of 2025. Please be wary of geolocations by both the Ukrainian and Russian sides in this direction. Both sides have propaganda goals to show themselves as winning in this area. 1:44 in the attached link: This was also found 50 …
🖕4👍3
🚨GEOLOCATION CLARIFICATION 🚨 Regarding a recent geolocation of Ukrainian Forces in the settlement of Zirka in the Komar Direction. On August 7th, a geolocation was posted with the claim that a Ukrainian position was hit by the 80th tank regiment in Zirka. Now, the geolocation itself seems almost correct but there are some glaring issues when viewed upon closer inspection. Circled to the left of the bottom stack of …
👍2
Showing the 7 most recent of 7 posts we hold for @andreevkamapping. 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Andreevka Mapping” (@andreevkamapping), 236 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/andreevkamapping.
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.