KOOP Высосала душу белого ты что Шан Цзун

Channel
𝕂𝔸ℤ𝔸ℕ𝕊𝕂𝕀𝕀
@kazanskiifm
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
31subscribers
+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 | -1002061444792 |
|---|---|
| Type | Channel |
| Username | @kazanskiifm |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/kazanskiifm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:15 | 31 | no change |
| 7 Aug 2026, 13:44 | 31 | first reading |
Engagement
19 posts held, back to 23 November 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 pageof 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 19 posts for this entry, the most recent from 24 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 23
- Videos
- 68
- Links
- 42
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.
- Video runtime
- 2m 49s
- Average length
- 19s
Measured directly from 9 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.
Recent posts
Photo, posted without a caption
Ссылки на видосы в ТТ потом добавлю
ПУСТОЙ ВОКЗАЛ Я ты две судьбы что одной стать не смогли
WANT SO MORE Настолько люблю рэп я слушаю даже своих оппов
Хенни Я позвонил своей бывшей сказал что я её люблю
Birds Птицы прилетают ко мне с юга УР УР
Perfect Timing Бесят вспышки камер, красивая одежда
†𝙴𝙳𝙸𝚃 - 𝙰𝙻𝙱𝚄𝙼 «𝙵𝚘𝚞𝚗𝚍 𝚃𝚊𝚙𝚎𝚜»† 𝙳𝙰𝚃𝙴 𝙳𝚁𝙾𝙿 - 𝟸𝟾.𝟶𝟷.𝟸𝟶𝟸𝟼 𝙼𝚂𝙲 𝚃𝙸𝙼𝙴: 𝟶:𝟶𝟶
С новым годом иуууу🎄🥳
Posted without readable text
i miss the old Kanye
Showing the 12 most recent of 19 posts we hold for @kazanskiifm. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“𝕂𝔸ℤ𝔸ℕ𝕊𝕂𝕀𝕀” (@kazanskiifm), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/kazanskiifm.
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.