Telegram RegisterThe public register of Telegram

Channel

Timeweb.Cloud News

@timewebru

Verified by Telegram

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

17,133subscribers

+37 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001071347514
TypeChannel
Username@timewebru
Created4 April 2017measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/timewebru

Growth

17,09617,13717,116.55 August 2026 — 17,096 subscribers6 August 2026 — 17,096 subscribers6 August 2026 — 17,097 subscribers7 August 2026 — 17,110 subscribers8 August 2026 — 17,121 subscribers9 August 2026 — 17,129 subscribers10 August 2026 — 17,133 subscribers11 August 2026 — 17,137 subscribers12 August 2026 — 17,136 subscribers13 August 2026 — 17,133 subscribers17,1335 August 202613 August 2026
10 measurements spanning 7 days, net +37. 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 17,090–17,143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:5317,133-3
12 Aug 2026, 00:3217,136-1
11 Aug 2026, 01:4117,137+4
10 Aug 2026, 02:1117,133+4
9 Aug 2026, 04:1117,129+8
8 Aug 2026, 05:3317,121+11
7 Aug 2026, 04:4317,110+13
6 Aug 2026, 04:4017,097+1
6 Aug 2026, 02:1817,096no change
5 Aug 2026, 23:2017,096first reading

Engagement

17 posts held, back to 13 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
31.3%
avg views ÷ 17,133 subscribers
Avg views / post
5,370
16 posts measured
Reaction rate
1.02%
reactions ÷ views · ER floor
Posts in window
16
of 17 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held17 (13 July 202612 August 2026)
Views total85,920
Reactions total876
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00:39 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.

What this channel posts

Video runtime
1m 03s
Average length
21s

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

929 reactions across 17 posts, in 22 distinct kinds. The most used accounts for 26.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
24526.4%
🔥22223.9%
👍12813.8%
929.90%
❤‍🔥657.00%
🎉616.57%
👏192.05%
🤝161.72%
👌151.61%
💔121.29%
🕊111.18%
🍾101.08%
🙏101.08%
🌚60.646%
🏆40.431%
🤓30.323%
20.215%
💯20.215%
🤗20.215%
🤩20.215%
2 further kinds20.215%

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

Measured over the 17 most recent posts we hold, published 13 July 2026 to 12 August 2026, 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

12 Aug 2026, 14:37 UTC≈1,980 views37 reactionsread 13 August 2026
Video

Одно приложение хорошо, а два — лучше Сделали то, что вы часто просили в идеях (раз, два, три). Теперь в App Platform копию приложения можно создать также, как копию облачного сервера. Пригодится, когда: 1️⃣ Пользователи в другом регионе — разворачиваете копию ближе к ним и снижаете задержки. 2️⃣ Подбираете конфигурацию — поднимаете клон на других ресурсах и сравниваете с оригинальным приложением 3️⃣ Нужен резер

🔥2188

11 Aug 2026, 16:43 UTC≈2,960 views57 reactionsread 13 August 2026
Photo

Эволюция ченжлога на сайте Многие из вас предлагают идеи по развитию продуктов и следят за обновлениями. Чтобы отслеживать релизы было проще, даже если пропустили дайджест, мы переделали старый ченжлог в «Журнал обновлений». В нем записана вся история релизов, изменений и исправлений багов с лета 2024 года. Что появилось: 1️⃣ Блок «Запланировано» — что сейчас в работе и выйдет в ближайшее время. Прежде чем нести ф

27🔥18👍8🏆3👏1

10 Aug 2026, 14:50 UTC≈3,480 views53 reactionsread 13 August 2026
Photo

Ctrl+Z для баз данных Классическая ситуация — наводите порядок в панели и случайно удаляете нужный кластер. Или перепутали прод с тестовым и выполнили команду удаления не в том окне. Чтобы избежать потери данных (а еще кучи времени и нервов) — запустили функцию отмены удаления базы данных. С ней удаленный кластер можно бесплатно восстановить в течение 72 часов со всеми данными, резервными копиями и конфигурацией.

🔥22👏1612👍2🕊1

7 Aug 2026, 14:29 UTC≈4,840 views45 reactionsread 13 August 2026
Photo

Никакого отпуска для июльских релизов Главная новость месяца — при создании первого AI-агента начисляем до 12,5 млн токенов. Если тратить по токену в секунду, хватит почти до конца года. А еще успели разогнать создание облачных серверов до 30 секунд, добавить предпросмотр файлов в S3 и подкинуть обновлений в App Platform. Вспоминаем главные обновления в карточках и смотрим подробнее в блоге →

20🎉147🤗21🙏1

5 Aug 2026, 14:56 UTC≈5,420 views38 reactionsread 13 August 2026
Video

Все нужное в одном месте Посмотрели на количество ваших реакций под постом про режим стримера, поэтому расскажем и о других UX-фичах этой недели. Сервисов у нас много, а новые продолжают появляться. Чтобы не тратить драгоценные клики, сделали «Избранное». В него можно закрепить любой раздел или отдельный сервис — наводите курсор на нужный пункт и отмечаете звездочкой. Заодно обновили настройки доступа для тех, кт

15🔥13🍾54🙏1

4 Aug 2026, 14:48 UTC≈4,780 views45 reactionsread 13 August 2026
Photo

Почти 7000 приложений на App Platform Как бы ни росло количество ваших фронтенд- и бэкенд-приложений, главное — предсказуемая сборка и понятная картина после деплоя. С этим помогают три инструмента: 1️⃣ Стенды для проверки релизов Копия приложения, чтобы протестировать изменения: поднимаете стенд, кидаете ссылку команде, собираете правки и только потом выкатываете в прод. Подробнее о настройке стендов → в доке.

1817👍10

3 Aug 2026, 15:59 UTC≈4,870 views104 reactionsread 13 August 2026
Video

Режим стримера 🎮 Теперь можно спокойно снимать скринкасты, стримить работу в панели или шарить экран на демо-звонке. Нам, кстати, тоже стало заметно проще записывать для вас инструкции. Все потому, что в панели появился режим стримера. Включаете — и панель сама блюрит конфиденциальные данные: ➖ Публичные IP-адреса ➖ Баланс ➖ Личные данные: ФИО, телефон, email ➖ Домены и почтовые ящики Пока переключатель в меню пр

🔥59👍2315👏2🤩2🌚1🦄1🙏1

31 Jul 2026, 15:01 UTC≈6,530 views43 reactionsread 13 August 2026
Photo

Выручка выросла в 32 раза за два года Такой цифрой поделился Metamentor. Их команда делает AI под заказ и за месяц внедряет его в контур клиента. Типичные запросы от заказчиков — речевая аналитика, боты поддержки, обработка документов. Началось все с хакатона в 2023 году. Трое студентов собрали прототип за неделю, взяли третье место и вскоре получили первый заказ. Сейчас в Metamentor работают 50+ человек, 30 из них

🔥2012❤‍🔥6🤓3💯2

30 Jul 2026, 16:28 UTC≈6,310 views72 reactionsread 13 August 2026
Photo

Ситуация: с 1 сентября у всех регистраторов доменов .ru .рф и .su должна быть кнопка идентификации владельца, которая подтягивает данные через ЕСИА. Видим, что вы переживаете, а где же эта кнопка у нас. Ответ в карточках 👆🏻

👍38👌14🕊10🤝43❤‍🔥1🌚1🏆1

30 Jul 2026, 14:08 UTC≈5,750 views43 reactionsread 10 August 2026

⚡️ Вернули регу в СПб Можно успеть, пока снова не разобрали. Заказать облачный сервер → Kubernetes, Managed Databases, S3 и App Platform в этой локации тоже в строю.

🎉20107🍾4🍓1👍1

29 Jul 2026, 15:20 UTC≈6,030 views71 reactionsread 10 August 2026
Photo

Запросы к российским API без ошибок TLS Многие российские сервисы работают на сертификатах Минцифры (Russian Trusted CA). Только у приложений их по умолчанию нет, а если их не добавить — соединение обрывается с ошибкой проверки. Теперь в App Platform можно включить поддержку сертификатов Минцифры — сразу при создании приложения или в настройках уже существующего. Что дают сертификаты: 1️⃣ Приложение обращается к

25👍22💔12🙏7🌚4👌1

22 Jul 2026, 15:13 UTC≈6,900 views41 reactionsread 7 August 2026
Photo

Пак обновлений в AI Gateway разблокирован 🔒 Но сначала о другом. На днях опубликуем на Хабре исследование о том, сколько запросов к нашей доке приходит от AI-агентов. Спойлер: много! А теперь о двух важных релизах в AI Gateway: 1️⃣ Новые модели OpenAI: речь и изображения Добавили модели для синтеза и распознавания речи — GPT-4o mini TTS, GPT-4o mini Transcribe и GPT-4o Transcribe, а для генерации изображений — GP

2213❤‍🔥5🍾1

Showing the 12 most recent of 17 posts we hold for @timewebru. 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 — 156,268 of 1,160,990entries 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 3 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.

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

“Timeweb.Cloud News” (@timewebru), 17,133 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/timewebru.

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.