Telegram RegisterThe public register of Telegram

Channel

Роскомцензура

@rostxt

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

1subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001124766795
TypeChannel
Username@rostxt
DescriptionЦензура не может быть направлена против внешнего врага, она всегда работает только против собственных граждан...
CreatedBetween 1 June 2017 and 13 August 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/rostxt

Growth

17 August 2026 — 1 subscribers14 August 2026 — 1 subscribers7 August 202614 August 2026
2 measurements spanning 7 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 13:461no change
7 Aug 2026, 04:421first reading

Engagement

20 posts held, back to 13 August 2017the 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 20 posts for this entry, the most recent from 20 December 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Videos
2
Links
36

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

22 Mar 2019, 19:59 UTC11 viewsread 14 August 2026
Forwarded from @hidemyname_ru

Наша новая публикация на Хабре про интернет-цензуру в Китае: https://habr.com/ru/company/hidemy_name/blog/444230/ На реальном опыте от первого лица.

22 Mar 2019, 19:58 UTC8 viewsread 14 August 2026
Forwarded from @zatelecomFile

РКН тут запилил "памятку" для тех, кто хочет сделать публичный Wi-Fi. Краткое содержание: НИКАК (по мнению РКН)

26 Jan 2019, 01:13 UTCviews —

The account of the user that created this channel has been inactive for the last 11 months. If it remains inactive in the next 19 days, that account will self-destruct and this channel will no longer have a creator.

15 Jan 2019, 13:59 UTCviews —

The account of the user that created this channel has been inactive for the last 11 months. If the account of the creator remains inactive in the next 30 days, it will self-destruct and the channel will lose its creator.

6 Sept 2017, 08:42 UTC8 viewsread 14 August 2026
Forwarded from @botshares

Дуров устроил Тинькову «Стрейзанд» Создатель Telegram Павел Дуров опубликовал на своей странице во «ВКонтакте» видео с YouTube-канала Nemagia, посвящённое «Тинькофф банку» и Олегу Тинькову, и призвал распространять ролик, пока его не удалили по требованию Роскомнадзора. https://roem.ru/05-09-2017/258289/durov-vs-tinkoff/ Роскомнадзор предписал заблокировать ролик Немагии об опасностях кредитного рабства, где Михаи

27 Aug 2017, 22:15 UTC5 viewsread 14 August 2026

Павел Дуров написал большой пост, в котором ответил на вопрос "Почему Телеграм не использует End-to-end шифрование данных по умолчанию", описал архитектуру Телеграма и развеял популярные мифы. Коллеги из @tglive перевели этот пост для вас. https://goo.gl/oBk84X #статьи

27 Aug 2017, 22:12 UTC4 viewsread 14 August 2026

Павел Дуров прокомментировал статью TJ о разной реакции Telegram на угрозы блокировки мессенджера в России и Индонезии. "В то время как руководство Индонезии выступает в защиту права на конфиденциальность, в России принимаются антиконституционные законы против тайны переписки интернет-пользователей. Если просьбы правительства Индонезии сводились только к более эффективной блокировке публичных каналов с пропагандой И

14 Aug 2017, 01:23 UTC3 viewsread 14 August 2026

Как упростить себе жизнь за счет Telegram? Постараюсь ответить на этот вопрос в статье. http://telegra.ph/Avtomatizaciya-Telegram-07-26

13 Aug 2017, 23:41 UTC2 viewsread 14 August 2026

ELSA. Слежка без GPS модуля. Слитая уязмость ЦРУ. http://telegra.ph/Elsa---slezhka-za-peremeshcheniem-07-05

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

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

“Роскомцензура” (@rostxt), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/rostxt.

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.