Channel
@ekb_covid_bot_info
On this record: Topic · Growth · Engagement · Posts · Polls · Cite this entry
1,240subscribers
-8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001318758547 |
|---|---|
| Type | Channel |
| Username | @ekb_covid_bot_info |
| Created | 5 July 2020 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ekb_covid_bot_info |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 93% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 13:40 | 1,240 | -1 |
| 9 Sept 2026, 17:55 | 1,241 | -2 |
| 4 Sept 2026, 00:40 | 1,243 | -1 |
| 31 Aug 2026, 16:27 | 1,244 | -1 |
| 22 Aug 2026, 16:38 | 1,245 | -2 |
| 19 Aug 2026, 07:58 | 1,247 | -1 |
| 6 Aug 2026, 22:04 | 1,248 | no change |
| 6 Aug 2026, 20:46 | 1,248 | first reading |
17 posts held, back to 5 July 2020 — the 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 17 posts for this entry, the most recent from 1 February 2022. An engagement rate over an empty window would be a number about nothing.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 17 posts we hold for @ekb_covid_bot_info. 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.
The 6 most recent of 16 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Я:
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 17 most recent posts we hold, published 5 July 2020 to 1 February 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“ekb_covid_bot_info” (@ekb_covid_bot_info), 1,240 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ekb_covid_bot_info.
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.