сделано

Channel
shakirovskie.
@shakirovskie
On this record: Topic · Growth · Engagement · Posts · Cite this entry
54subscribers
-2 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 | -1002381295527 |
|---|---|
| Type | Channel |
| Username | @shakirovskie |
| Created | 11 January 2025 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/shakirovskie |
Topic
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 11:19 | 54 | -1 |
| 10 Sept 2026, 05:21 | 55 | -1 |
| 10 Aug 2026, 07:46 | 56 | no change |
| 7 Aug 2026, 15:44 | 56 | first reading |
Engagement
7 posts held, back to 11 January 2025 — 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 7 posts for this entry, the most recent from 22 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
хотите возвращение?
🔔 |💼join in the chat of shakirovskie | 1️⃣подписка на канал 2️⃣ ознакомление с правилами 3️⃣подать заявку в чат
RULES OF CHAT SHAKIROVI 🌟 1. Запрещаются любые обсуждения политики, а так же оскорбления нации и религии. 2.Не устраивать ссоры или переходить в лс. Если ссора и началась, зовем администрацию и дальше не продолжаем. 3. Запрещается неуважительное отношение к участникам и так же соответственно администрации, постоянные оскорбления или сплошной рофл-бан. следим за языком. 4. На счет реста пишем администрации. 5. Спам с…
🥳😚🤨🙃🥺🙄 Owner ✍️ a.l Co-owner ✍️ @PUM2Q Admin for video ✍️ Admin for chat ✍️
Добро пожаловать в семью шакировских. 😴🥳🫥🥸🥺🫥 ✍️ с этого дня все названия «shakirovi, shakirovskie, шакировы или шакировские» принадлежат только нам. если мы заметим такое же название у других конференций, то мы имеем полное право попросить поменять название. если последует отказ, будем принимать меры.
Channel created
Showing the 7 most recent of 7 posts we hold for @shakirovskie. 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.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“shakirovskie.” (@shakirovskie), 54 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/shakirovskie.
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.