Telegram RegisterThe public register of Telegram

Channel

mdk.mrpl

@mdkmrpl

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

2,624subscribers

-4 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001467291521
TypeChannel
Username@mdkmrpl
Created1 May 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 13 August 2026
On Telegramt.me/mdkmrpl

Growth

2,6242,6282,6266 August 2026 — 2,628 subscribers6 August 2026 — 2,628 subscribers7 August 2026 — 2,627 subscribers10 August 2026 — 2,624 subscribers6 August 202610 August 2026
4 measurements spanning 4 days, net -4. 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 2,623–2,629 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 03:212,624-3
7 Aug 2026, 06:212,627-1
6 Aug 2026, 11:072,628no change
6 Aug 2026, 10:012,628first reading

Engagement

16 posts held, back to 1 October 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 16 posts for this entry, the most recent from 9 May 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14m 40s
Average length
3m 40s

Measured directly from 4 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

734 reactions across 16 posts, in 8 distinct kinds. The most used accounts for 57.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
42157.4%
😢14419.6%
👍8912.1%
🤬496.68%
🤡253.41%
💯40.545%
😁10.136%
🤔10.136%

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

Measured over the 16 most recent posts we hold, published 1 October 2023 to 9 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

9 May 2024, 20:10 UTC≈4,990 views33 reactionsread 7 August 2026

Пишуть, що у Маріуполі 💥

👍285

7 May 2024, 12:21 UTC≈5,070 views88 reactionsread 7 August 2026
Forwarded from @lachentytPhoto

Загинув 21-річний Назарій Гринцевич "Грінка", воїн бригади «Азов». Назар пройшов полон і був одним з наймолодших захисників Азовсталі. Після полону він продовжував свою службу та завжди бився як рекс і завдяки вам ви закрили не один збір для його підрозділу. Вічна пам’ять і честь тобі, друже. Для тих хто бажає допомогти родині

😢82🤡41😁1

11 Mar 2024, 08:25 UTC≈5,090 views68 reactionsread 7 August 2026
Forwarded from @lachentytPhoto

Напевно, я буду першим режисером, який скаже це тут: я хотів би, щоб цього фільму не було. Я хотів би, щоб Росія ніколи не нападала на Україну, ніколи не окуповувала наші міста. Я б віддав цю нагороду за те, щоб Росія не вбивала десятки тисяч моїх співвітчизників-українців, звільнила всіх українських військових і цивільних, які в полоні, — режисер фільму Мстислав Чернов Потужна промова.

63👍3🤡2

11 Mar 2024, 08:24 UTC≈3,810 views48 reactionsread 7 August 2026
Forwarded from @lachentytPhoto

Фільм "20 днів у Маріуполі" отримав Оскар у категорії "Найкращий документальний фільм". Це перший Оскар в історії України 🥺

😢2514🤡5💯4

3 Jan 2024, 18:29 UTC≈4,160 views82 reactionsread 7 August 2026
Forwarded from @lachentytVideo

НАРЕШТІ ОБМІН З російського полону повернули понад 200 наших воїнів і цивільних. Солдати, сержанти, офіцери. Воїни Збройних Сил, Національної гвардії, ВМС, прикордонники. Частина захисників боронила Маріуполь та «Азовсталь». УРАА

74👍4🤡4

3 Jan 2024, 18:29 UTC≈4,590 views66 reactionsread 7 August 2026
Forwarded from @lachentyt

230 наших повернули 🫂 Це найбільший обмін

63👍1🤔1🤡1

31 Dec 2023, 22:14 UTC≈4,380 views94 reactionsread 7 August 2026

З НОВИМ РОКОМ! Дякую нашим захисникам за те, що я можу зустріти цей рік 🙏

86👍8

24 Nov 2023, 18:56 UTC≈5,040 views12 reactionsread 7 August 2026

Друзі, доброго вечора. Прохання - додати у сторіс. Дякую свідомим людям! https://www.instagram.com/reel/C0Bs1CuqhZp/?igshid=MzY1NDJmNzMyNQ==

10👍2

5 Nov 2023, 18:41 UTC≈6,340 views51 reactionsread 7 August 2026
Forwarded from @lachentytVideo

ого!

👍389🤬4

5 Nov 2023, 18:41 UTC≈4,040 views44 reactionsread 7 August 2026
Forwarded from @lachentytPhoto

Десь між Новоазовськом та Сєдовим (під Маріуполем), глибокий тил т.о. України. Дуже активно детонує 😍

37👍5🤡1🤬1

7 Oct 2023, 06:56 UTC≈5,290 views2 reactionsread 7 August 2026
Photo

Сьогодні день народження у хуйла. Напишіть свої побажання для нього у коментарях 👇

🤬2

5 Oct 2023, 13:59 UTC≈4,630 views12 reactionsread 7 August 2026
Forwarded from @lachentyt

49 загиблих …

🤬10😢2

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“mdk.mrpl” (@mdkmrpl), 2,624 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/mdkmrpl.

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.