Channel
@dk_mayakprk
On this record: Topic · Growth · Engagement · Posts · Cite this entry
601subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001548358901 |
|---|---|
| Type | Channel |
| Username | @dk_mayakprk |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/dk_mayakprk |
Local community — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 3 Oct 2026, 23:19 | 601 | -1 |
| 10 Sept 2026, 07:36 | 602 | +1 |
| 31 Aug 2026, 05:34 | 601 | -1 |
| 23 Aug 2026, 16:28 | 602 | -2 |
| 16 Aug 2026, 21:04 | 604 | -1 |
| 8 Aug 2026, 03:05 | 605 | no change |
| 7 Aug 2026, 20:54 | 605 | first reading |
3 posts held, back to 7 August 2026 — 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
В Кузбассе около восьми тысяч спортивных сооружений. Регулярно тренируются более полутора миллионов жителей региона. Некоторые из них выбирают довольно экзотичные виды спорта. Накануне Дня физкультурника рассказываем о самых необычных доступных вариантах активного образа жизни.
Signed ГосПаблики
В Кузбассе около восьми тысяч спортивных сооружений. Регулярно тренируются более полутора миллионов жителей региона. Некоторые из них выбирают довольно экзотичные виды спорта. Накануне Дня физкультурника рассказываем о самых необычных доступных вариантах активного образа жизни.
Signed ГосПаблики
🤪 Русская классика на языке смайликов. Визуальные загадки по мотивам известных произведений: от «Муму» до «Человека в футляре». Три уровня сложности, охватывающие разные эпохи и сюжеты отечественной литературы. Какое произведение оказалось самым неожиданным?
Signed ГосПаблики
Showing the 3 most recent of 3 posts we hold for @dk_mayakprk. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“🏛️ДК им.Маяковского” (@dk_mayakprk), 601 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/dk_mayakprk.
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.