Telegram RegisterThe public register of Telegram

Channel

КПП Королевского Союза

@resp_durka

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

21subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001436454804
TypeChannel
Username@resp_durka
DescriptionВход в виртуальное государство. https://t.me/+ZhEpimZjCSc2Nzky @royal1union
Created4 December 2020measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/resp_durka

Growth

2110 Aug 2026, 14:51 — 21 subscribers11 Aug 2026, 14:01 — 21 subscribers10 Aug 2026, 14:5111 Aug 2026, 14:01
2 measurements taken within a single day. 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 20–22 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 14:0121no change
10 Aug 2026, 14:5121first reading

Engagement

8 posts held, back to 4 December 2020the 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 8 posts for this entry, the most recent from 7 July 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Links
6

Lifetime counters from Telegram’s own channel header, read 11 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.

Recent posts

7 Jul 2024, 14:41 UTC197 viewsread 11 August 2026
Photo

ВХОД В ГОСУДАРСТВО: Валирия: https://t.me/+ZhEpimZjCSc2Nzky Дурка: https://t.me/republic_durka #rp #virtualstate #roleplay

7 Jul 2024, 14:41 UTC100 viewsread 11 August 2026
Forwarded from @royal1union

Тень грядущих перемен легла на Королевский Союз. Глас сей, летящий на крыльях вестников, да достигнет каждого очага, от цветущих долин Валирии до суровых твердынь Дурки! История вершится на наших глазах. Наступил день, когда раздоры прошлого канули в Лету! По воле Короля Алексея Кудлы из Дома Кудлов, Баксей прозванным, первого своего имени, владыки королевства и защитника державы, и мудрому совету Малого Совета в с

16 Oct 2022, 17:28 UTC362 viewsread 11 August 2026
Forwarded from @royal1union

Сепаратизм и предательство. От имени члена Президиума Дмитрия Кудлы, от имени Короля Алексея Бакси, от имени Сената, от имени большинства жителей Валирии и Королевского Союза в целом, Малый Совет Королевского Союза публикует официальное заявление, касательно Дурчанской Народной Республики и будущего нашей с вами страны. В течение долгого времени мы страдали от ужасной проблемы, которая усугублялась, пока не стала н

25 Feb 2021, 14:06 UTC≈3,480 viewsread 11 August 2026
Photo

ВХОД В ГОСУДАРСТВО: Валирия: https://t.me/+ZhEpimZjCSc2Nzky Дурка: https://t.me/republic_durka #rp #меморандум #virtualstate #roleplay

6 Feb 2021, 20:59 UTC≈3,210 viewsread 11 August 2026
Photo

Если у вас есть данное ограничение, то чтобы обойти его, Вы должны:1) Открыть настройки; 2) Открыть вкладку «Конфиденциальность»; 3) Прокрутить вниз и найти строку «Материалы деликатного характера»;4) Выключить ограничения. Примечание: данное действие можно сделать только через ПК. https://t.me/+ZhEpimZjCSc2Nzky

11 Dec 2020, 22:02 UTC≈2,690 viewsread 11 August 2026

Виртуальное государство. Валирия: https://t.me/+ZhEpimZjCSc2Nzky Дурка: https://t.me/republic_durka

Showing the 8 most recent of 8 posts we hold for @resp_durka. 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.

Mentions

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

“КПП Королевского Союза” (@resp_durka), 21 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/resp_durka.

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.