Telegram RegisterThe public register of Telegram

Channel

Daryo | На русском

@daryo_russian

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,248subscribers

+0 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-1001890256525
TypeChannel
Username@daryo_russian
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/daryo_russian

Growth

1,2471,2491,2486 August 2026 — 1,248 subscribers6 August 2026 — 1,247 subscribers6 August 2026 — 1,247 subscribers9 August 2026 — 1,249 subscribers12 August 2026 — 1,248 subscribers6 August 202612 August 2026
5 measurements spanning 6 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”. The vertical axis spans 1,247–1,249 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 01:121,248-1
9 Aug 2026, 07:541,249+2
6 Aug 2026, 08:351,247no change
6 Aug 2026, 06:301,247-1
6 Aug 2026, 03:201,248first reading

Engagement

20 posts held, back to 5 August 2026the 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.

ERR · 30 days
9.61%
avg views ÷ 1,248 subscribers
Avg views / post
120
20 posts measured
Reaction rate
1.30%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 4 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (5 August 20266 August 2026)
Views total2,399
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 08:35 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.

Recent posts

6 Aug 2026, 08:00 UTC≈28 viewsread 6 August 2026
Photo

Проехать по платной дороге в Узбекистане можно будет по дорожным талонам Для проезда по платной дороге пользователь заключает публичный договор с оператором путем въезда на платную дорогу, оплаты проезда на пункте оплаты, а также приобретением дорожного талона. При этом на дороге должен быть обеспечен высокий скоростной режим и качественный сервис. Читать на сайте — https://daryo.uz/ru/uO47wtsDR 👉 Подпишитесь - @d

6 Aug 2026, 07:20 UTC≈49 viewsread 6 August 2026
Photo

Какая погода ожидается в Узбекистане 7 августа Температура в Ташкенте будет в пределах 35-37 градусов. Читать на сайте — https://daryo.uz/ru/0cvMypsDg 👉 Подпишитесь - @daryo_russian

6 Aug 2026, 06:30 UTC≈75 views2 reactionsread 6 August 2026
Photo

Узбекистан вывел Центральную Азию в мировые лидеры по туризму В 2025 году экспорт туруслуг в регионе достиг $9,9 млрд. Почти половина этой суммы — $4,8 млрд — пришлась на Узбекистан. Читать на сайте — https://daryo.uz/ru/Br61-tyvR 👉 Подпишитесь - @daryo_russian

6 Aug 2026, 05:41 UTC≈90 views1 reactionsread 6 August 2026
Photo

«Позорная махалля» и «Позорный дом» — хоким Чиназа ввел новые статусы для неблагоустроенных территорий Хоким района раскритиковал состояние махалли, отметив, что на территории не высажены цветы и базилик, не скошена трава, а уже скошенная растительность не вывезена. Поэтому он распорядился установить на видном месте табличку с надписью «Позорная махалля». Читать на сайте — https://daryo.uz/ru/MARAJtsDR 👉 Подпишите

6 Aug 2026, 05:00 UTC≈95 viewsread 6 August 2026
Photo

FIFA столкнулась с жестким сопротивлением со стороны европейских лиг Ассоциация европейских профессиональных футбольных лиг — European Leagues заявила, что не поддержит решения FIFA об изменении действующих соревнований или организации новых турниров до тех пор, пока в системе управления организации не будут проведены реформы. Читать на сайте — https://daryo.uz/ru/Dw2l2psDR 👉 Подпишитесь - @daryo_russian

6 Aug 2026, 04:04 UTC≈103 viewsread 6 August 2026
Photo

В Ташкенте частично ограничили работу рынка «Куйлюк» На территории рынка выявили многочисленные нарушения требований пожарной безопасности, которые могут привести к возникновению пожара и создать угрозу жизни, здоровью и имуществу людей. Читать на сайте — https://daryo.uz/ru/WHhBOpyvR 👉 Подпишитесь - @daryo_russian

6 Aug 2026, 03:10 UTC≈103 viewsread 6 August 2026
Photo

Сегодня температура воздуха по Узбекистану может повыситься до 38 градусов В горных районах возможны кратковременные дожди с грозами. Читать на сайте — https://daryo.uz/ru/WrTzvtsvg 👉 Подпишитесь - @daryo_russian

5 Aug 2026, 16:50 UTC≈143 viewsread 6 August 2026
Photo

Фабио Каннаваро: «Я единственный в мире глупый тренер, который взял на ЧМ футболиста с травмой» Главный тренер сборной Узбекистана объяснил ситуацию с полузащитником Жалолиддином Машариповым, который не смог принять участие в мундиале. Читать на сайте — https://daryo.uz/ru/QLjqm5yvg 👉 Подпишитесь - @daryo_russian

5 Aug 2026, 16:10 UTC≈140 viewsread 6 August 2026
Photo

В плену Украины находятся граждане 51 страны, воевавшие на стороне России Среди воюющих в рядах российской армии числятся и граждане Узбекистана. Омбудсман Украины заявил, что важно открыто информировать международное сообщество о правовых последствиях участия в войне на стороне России. Читать на сайте — https://daryo.uz/ru/ZSS0eKyDg 👉 Подпишитесь - @daryo_russian

5 Aug 2026, 15:40 UTC≈148 viewsread 6 August 2026
Photo

Как работает DMED: откуда берутся ошибочные данные, дубли аккаунтов и очереди по онлайн-записи В интернете пользователи нередко задаются вопросами о работе цифровой медицинской платформы DMED. Одни сообщают о посещениях поликлиник, которых на самом деле не было, другие сталкиваются с дублирующимися профилями, отсутствием диагнозов в электронной медицинской карте или очередями, несмотря на предварительную онлайн-запи

5 Aug 2026, 14:51 UTC≈134 viewsread 6 August 2026
Photo

Обвал края котлована: Жители несколько месяцев предупреждали об опасности, но стройка продолжалась В махалле «Орзу» Алмазарского района Ташкента обрушился край котлована, вырытого под строительство гостиницы. В результате пострадал один из рабочих, был поврежден участок дороги, оборван электрический кабель, а жители ближайших домов на некоторое время остались без электричества. Также возникли перебои с водоснабжение

5 Aug 2026, 13:40 UTC≈137 viewsread 6 August 2026
Photo

Какая погода ждет жителей Узбекистана 6 августа В Андижанской, Наманганской и Ферганской областях местами переменная облачность, местами возможен кратковременный дождь, гроза. В остальных регионах без осадков. Читать на сайте — https://daryo.uz/ru/Y4gX7KyDR 👉 Подпишитесь - @daryo_russian

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

Citation-graph rank

Citation-graph rank — 296,411 of 1,340,412entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by 2 registered channels — 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.

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

“Daryo | На русском” (@daryo_russian), 1,248 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/daryo_russian.

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.