Telegram RegisterThe public register of Telegram

Channel

Белая река

@uraldan

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

372subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001097003484
TypeChannel
Username@uraldan
Created6 December 2016measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/uraldan

Growth

3726 Aug 2026, 00:23 — 372 subscribers6 Aug 2026, 20:33 — 372 subscribers6 Aug 2026, 00:236 Aug 2026, 20:33
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 371–373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 20:33372no change
6 Aug 2026, 00:23372first reading

Engagement

14 posts held, back to 16 January 2024the 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 14 posts for this entry, the most recent from 23 August 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
315
Videos
3
Links
150

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

23 Aug 2024, 10:57 UTC≈1,090 viewsread 6 August 2026

охереть у телеграм-канала на 10к подписчиков есть управляющий совет (остальное не читал)

26 Jul 2024, 11:56 UTC817 viewsread 6 August 2026

наконец — то, ради чего всё и затевалось: передача «диалоги о футболе»

26 Jul 2024, 11:56 UTC≈1,100 viewsread 6 August 2026
Forwarded from @thecenotaphPhoto

И вот он — долгожданный разговор об исторических смыслах российского футбола. Руслан Гафаров, Сергей Простаков и Егор Сенников решили ответить на вопрос: что заставляет в 2024 году следить за российским футболом? Но в итоге их разговор от обсуждения чисто футбольных вещей быстро перешёл к главными сюжетам издания «Кенотаф»: почва и судьба, время и место, память и забвение, напряжение исторического момента. Самое в

22 Jul 2024, 15:00 UTC≈20,700 viewsread 6 August 2026

Олег Кашин мой друг https://telegra.ph/K-obyavleniyu-menya-v-rozysk-Memorandum-07-22

14 Jun 2024, 18:00 UTC≈1,080 viewsread 6 August 2026
Forwarded from @NoodleRemoverPlus

Нужно ли было сдать Ленинград, чтобы сберечь сотни тысяч жизней?

27 Mar 2024, 17:03 UTC≈1,400 viewsread 6 August 2026
Photo

Задача: найдите на карточках хотя бы один случай, где таджики рассказывают, как они столкнулись с ксенофобией На двоих, по их мнению, косо смотрят, остальные пересказывают чужие истории Претензии к коллегам, не к таджикам

1 Mar 2024, 11:20 UTC≈1,250 viewsread 6 August 2026

нумерология в издании кенотаф (все подписались уже?) https://t.me/thecenotaph/1071

27 Feb 2024, 12:12 UTC≈1,230 viewsread 6 August 2026
Photo

Эдак коллеги скоро дойдут и до восхищённых болгар!

3 Feb 2024, 18:08 UTC≈24,500 viewsread 6 August 2026

Сегодня в «Кенотафе» напомнил про важный для меня текст, потому здесь последует личное дополнение. https://t.me/thecenotaph/1006 Я работаю в медиа десять с небольшим лет, мало по меркам профессии и много по сравнению с младшим штатом нынешних оппозиционных медиа, ровесниками меня описанных событий. После увольнения с «Дождя» за вынужденной подписью «по собственному» я полтора года вёл соцсети проектов ВГТРК в поис

27 Jan 2024, 16:59 UTC≈1,140 viewsread 6 August 2026
Photo

Мощный копирайт у коллег, такой прямо революционно-пономарёвский (деньги собирают)

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

Mentions

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

“Белая река” (@uraldan), 372 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/uraldan.

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.