Telegram RegisterThe public register of Telegram
Telegram profile photo for DIMAP.LIVE - Новини Проєкту, Мапа Тривог та загроз, руху цілей в реальному часі 24/7

Channel

DIMAP.LIVE - Новини Проєкту, Мапа Тривог та загроз, руху цілей в реальному часі 24/7

@di_ukraine

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

8,936subscribers

+171 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002881028954
TypeChannel
Username@di_ukraine
DescriptionЄдиний офіційний канал проєкту DIMAP в телеграм. РЕКЛАМ НЕ БЕРЕМО! Ми волонтерський сервіс! Співпраця/підтримка напряму з розробниками: @widesystems Для інших питань/пропозицій: t.me/di_ukraine?direct
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/di_ukraine

Growth

8,7658,9368,850.57 August 2026 — 8,765 subscribers7 August 2026 — 8,765 subscribers8 August 2026 — 8,795 subscribers11 August 2026 — 8,869 subscribers14 August 2026 — 8,936 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net +171. 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 8,739–8,962 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 12:288,936+67
11 Aug 2026, 10:178,869+74
8 Aug 2026, 15:448,795+30
7 Aug 2026, 19:178,765no change
7 Aug 2026, 19:038,765first reading

Engagement

22 posts held, back to 30 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 13 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
72.9%
avg views ÷ 8,936 subscribers
Avg views / post
6,510
7 posts measured
Reaction rate
0.489%
reactions ÷ views · ER floor
Posts in window
7
of 22 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 August 2026
Posts held22 (30 May 202611 August 2026)
Views total45,580
Reactions total223
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 16:26 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
33
Videos
1
Links
67

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

871 reactions across 22 posts, in 4 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 538217185819808479951258.8%
custom 537981176507899768122325.6%
custom 538218732867028265510712.3%
custom 5382135879257044651293.33%

Custom emoji. Every 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 counts beside them areTelegram’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 22 of the 22 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 871reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 30 May 2026 to 11 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.

Telegram Stars

Stars received
12
across the posts below
Posts paid on
7
of 22 we hold a reading for · 32%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @di_ukraine. 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 22 most recent posts we hold for this entry, published 30 May 2026 to 11 August 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.

Recent posts

11 Aug 2026, 10:07 UTC≈3,640 views48 reactionsread 15 August 2026

Важливо для розробників, які користуються DIMAP-API! Будьте готові протягом наступних 14 днів перейти на новий енд-поінт. Детальніше повідомимо окремо. Також буде надано документацію. Повністю безкоштовно. Ми дуже пишаємося усіма розробками, які націлені на покращення інформування наших людей та готові їх підтримувати. 🐱

custom 538217185819808479934custom 53821873286702826559custom 53798117650789976815

11 Aug 2026, 08:08 UTC≈3,890 views23 reactionsread 15 August 2026

Доброго ранку! Сайт вже працює. Стався збій на стороні провайдера. Вибачте за незручності.

custom 538217185819808479920custom 53798117650789976813

6 Aug 2026, 09:35 UTC≈7,850 views23 reactions1 Starread 15 August 2026

Прокинулися. Разом з бетою. В разі чогось - пишіть. На звʼязку 24/7 t.me/di_ukraine?direct

custom 538217185819808479915custom 53821873286702826556custom 53798117650789976812

6 Aug 2026, 08:52 UTC≈7,540 views24 reactionsread 15 August 2026

Лежим. команда вже працює над вирішенням проблеми.

custom 537981176507899768121custom 53821718581980847992custom 53821873286702826551

6 Aug 2026, 00:01 UTC≈7,790 views19 reactionsread 15 August 2026

Також зараз тестуємо найшвидший метод передачі даних для клієнта, з мінімальною затримкою. Тому якщо бачите збої - напишіть, будь ласка, в приватні каналу. Зробимо проєкт кращий разом! Наступне оновлення цієї Бети орієнтовно завтра по обіді. До зустрічі.

custom 537981176507899768117custom 53821718581980847992

5 Aug 2026, 23:48 UTC≈7,500 views26 reactions3 Starsread 15 August 2026

Настав цей момент! Пілотний DIMAP 3.0 вже в доступі за dimap.live/beta Що нового? Повністю нова система показу цілей. Мінімальна затримка. Відсутність дублікатів (!) Точність 9 з 10 Станом на зараз в цій пілотній версії доступно лише показ цілей. Без тривог та стрічки. З часом функціонал буде додаватися. Всім тихої ночі.

custom 538217185819808479920custom 53821873286702826554custom 53798117650789976812

4 Aug 2026, 10:53 UTC≈7,370 views60 reactionsread 15 August 2026

Анонс: Пілотний 3.0 буде в доступі об 01:00. 6 серпня. До зустрічі.

custom 538217185819808479940custom 538218732867028265511custom 53798117650789976819

14 Jul 2026, 05:40 UTC≈16,700 views57 reactionsread 15 August 2026

Шановні користувачі DIMAP. З 10:00 по 12:00 на платформі будуть проводитися перші технічні роботи, для з метою оновлення до 3.0. Сервіс в цей період працюватиме, але пізніше доведеться всім оновити сторінку, щоб він продовжував роботу. Пізніше, нам доведеться до години часу його вимкнути, про це повідомимо окремо.

custom 537981176507899768128custom 538217185819808479919custom 538218732867028265510

13 Jul 2026, 21:02 UTC≈16,500 views32 reactionsread 15 August 2026

Стрічка вийшла з ладу: Проблеми на стороні Telegram. Вибачте за тимчасові незручності. Щодо 3.0 - очікуйте анонс протягом дня. Вже все є 🤫

custom 538217185819808479929custom 53821873286702826553

9 Jul 2026, 21:02 UTC≈18,800 views57 reactions2 Starsread 15 August 2026

Всім вітання! Настав час для 3.0. Нажаль, застосунок на IOS вже вкотре відхилили, тому ми подали його знову. Щодо веб-версії, впровадження оновлення буде поступове. Деталі згодом. Спокійної ночі всім.

custom 537981176507899768140custom 53821718581980847999custom 53821873286702826558

25 Jun 2026, 20:34 UTC≈23,000 views42 reactionsread 15 August 2026

Виявлено інцидент: Житомирська область: тимчасово без показу цілей. Орієнтовне вирішення проблеми до 23:45. Вибачте за незручності.

custom 538217185819808479936custom 53821873286702826556

15 Jun 2026, 07:16 UTC≈25,300 views28 reactionsread 15 August 2026

Всім доброго ранку! Питання 1: Вночі трішки алгоритм безпеки зламався, і повідводив збиті шахеди трішки в сторону заходу, потім прибрав. Питання 2: Розбирали тут: https://www.threads.com/@dimap_live/post/DZmPy67F_WX Всім спокійного дня.

custom 538217185819808479919custom 53821873286702826556custom 53798117650789976813

Signed Sasha

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 1,427,058 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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.

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

“DIMAP.LIVE - Новини Проєкту, Мапа Тривог та загроз, руху цілей в реальному часі 24/7” (@di_ukraine), 8,936 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/di_ukraine.

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.