Telegram RegisterThe public register of Telegram
Telegram profile photo for Kvede Новости

Channel

Kvede Новости

@KvedeNews

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

19subscribers

+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-1002367976193
TypeChannel
Username@KvedeNews
DescriptionПубликуем важную и интересную информацию о проекте Kvede Bot. Правила общения просты - человеческое отношение и взаимоуважение друг к другу. За мат, флуд и спам - мют да бан. Чат поддержки: @KvedeSupport
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live15 September 2026
Measurements held2
On Telegramt.me/KvedeNews

Growth

197 August 2026 — 19 subscribers11 August 2026 — 19 subscribers7 August 202611 August 2026
2 measurements spanning 4 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 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 17:0119no change
7 Aug 2026, 14:2919first reading

Engagement

20 posts held, back to 21 March 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 page of 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 22 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
54
Links
23

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.

Reaction mix

31 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 38.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1238.7%
🔥1032.3%
412.9%
😁412.9%
😢13.23%

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

Measured over the 20 most recent posts we hold, published 21 March 2026 to 22 July 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

22 Jul 2026, 08:56 UTC13 views2 reactionsread 11 August 2026
Photo

Кратко о том как "невидимые сообщения" влияют на защиту от спама. За последние трое суток в чат было опубликовано всего одно спам-сообщение. Для сравнения, до этого бот отлавливал, в среднем, по 8-15 сообщений в сутки. Вывод: спам-боты пока что не научились работать с невидимками. Второй их плюс - они перестали захламлять чат :)

👍1🔥1

14 Jul 2026, 20:36 UTC20 views3 reactionsread 11 August 2026
Photo

Возвращаем "невидимые сообщения", или, как их ещё называют в Telegram, эфемеральные. Сообщения приходят в версии приложения 7.0.1 или выше. https://telegramdesktop.github.io/tdesktop/changelog/

👍3

14 Jul 2026, 19:27 UTC20 viewsread 11 August 2026

Отключили эфемеральные сообщения - не работает фича. Сообщения попросту не приходят к пользователям. Ждём пока Telegram их починит.

14 Jul 2026, 14:46 UTC19 viewsread 11 August 2026

Выкатили новую версию Изменения: - Приветственные сообщения теперь будут видимы только для их получателей. - Улучшили отлов цитат в сообщениях - Апгрейднули ядро Временные изменения: - Отключили админку (переписываем с нуля) - Отключены некоторые локализации. По завершении работ с апгрейдом админки, вернём локализации в лучшем виде!

30 Jun 2026, 15:51 UTC31 views2 reactionsread 11 August 2026

1-го июля с 12:00 до 20:00 по московскому времени состоится миграция инфраструктуры в новый дата-центр. Временный ДЦ, на котором размещено текущее оборудование, не обеспечил требуемого уровня надёжности.

👍2

12 Jun 2026, 14:13 UTC46 views3 reactionsread 11 August 2026

Восстановили новый старый сервер 😀

🔥3

5 Jun 2026, 10:31 UTC48 views2 reactionsread 11 August 2026

Перезапустили @KvedeBot без веб-интерфейса Бот работает в штатном режиме

2

5 Jun 2026, 07:30 UTC45 views1 reactionsread 11 August 2026

Не вывез сервер нагрузки 🥲 База рухнула

🔥1

2 Jun 2026, 20:44 UTC46 views1 reactionsread 11 August 2026
Photo

Интересные новости. На практике, @KvedeBot не может дотянуться до Telegram с российских серверов, так что ждём решения проблемы. В случае невозможности будем искать альтернативные методы запуска.

😢1

2 Jun 2026, 14:29 UTC42 viewsread 11 August 2026

Хостер сообщает о проведении внеплановых технических работах в дата-центре. Ориентировочное время завершения работ до 20:30 по московскому времени. До этого времени @KvedeBot будет работать нестабильно или не работать вовсе. UPD: обновлено время - до 02.06 23:00 по Москве UPD: обновлено время - до 03.06 18:00 по Москве UPD: обновлено время - до 03.06 23:30 по Москве

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

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.

“Kvede Новости” (@KvedeNews), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/KvedeNews.

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.