Channel
@k_zap
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3,689subscribers
+35 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001204164112 |
|---|---|
| Type | Channel |
| Usernames | @k_zap @k_zap_admin @k_zap_pravila |
| Created | 16 June 2019 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/k_zap |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 06:19 | 3,689 | +3 |
| 7 Sept 2026, 09:38 | 3,686 | -8 |
| 5 Sept 2026, 04:38 | 3,694 | +7 |
| 2 Sept 2026, 04:46 | 3,687 | +2 |
| 1 Sept 2026, 18:23 | 3,685 | -2 |
| 31 Aug 2026, 09:08 | 3,687 | +1 |
| 30 Aug 2026, 04:45 | 3,686 | -3 |
| 28 Aug 2026, 17:47 | 3,689 | +2 |
| 27 Aug 2026, 08:17 | 3,687 | +1 |
| 27 Aug 2026, 02:54 | 3,686 | +14 |
| 24 Aug 2026, 12:43 | 3,672 | no change |
| 24 Aug 2026, 07:25 | 3,672 | -3 |
| 22 Aug 2026, 17:58 | 3,675 | -2 |
| 21 Aug 2026, 02:23 | 3,677 | +4 |
| 20 Aug 2026, 17:12 | 3,673 | +2 |
| 19 Aug 2026, 12:46 | 3,671 | -1 |
| 17 Aug 2026, 16:47 | 3,672 | -3 |
| 17 Aug 2026, 12:15 | 3,675 | +5 |
| 16 Aug 2026, 17:22 | 3,670 | +5 |
| 14 Aug 2026, 03:57 | 3,665 | first reading |
4 posts held, back to 16 June 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 pages 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 4 posts for this entry, the most recent from 6 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
📌Кстати, оплату теперь мы можем принимать ПОДПИСЧИКАМИ! 📌(Как частично так и полностью) 1 (один) целевой подписчик (который ранее не был участником закрытой группы "Куплю Запчасти") = 100 рублей на Ваш баланс ....или если не нужно делать никаких публикаций, то 1 участник = 6 дней доступа к группе! Скопируйте этот текст 👇👇👇👇👇👇👇 Пришлите мне реферальную ссылку для добавления новых подписчиков в закрытую группу "Куп…
🔗Пригласительная ссылка: https://telegram.me/+Oi8qJ3SFwsE0OWQy 1) Вступайте в данное сообщество только если Вы полностью согласны с правилами этой закрытой группы! 2) После вступления, свяжитесь с админом, подтвердите что Вы не бот, и ограничения на публикации будут сняты! 3) По вопросам сотрудничества: 👇👇👇 https://telegram.me/k_zap_admin?direct 💳💳💸 Теперь Вы можете поддержать нас тут, через официального бота …
❗️ ПРАВИЛА ГРУППЫ ❗️ Ознакомьтесь... 1) В группе пишем только ЗАЯВКИ НА ЗАПЧАСТИ! В начале сообщения прописав любое из этих слов: Спрос 👈/👉 Куплю 👈/👉 Ищу В сообщении указываем непосредственно Вашу частную потребность, марка/модель техники, по возможности укажите и каталожные номера! (Скупка запчастей не является Вашей частной потребностью - это бизнес) Публикуя заявки, просьба делать это КОМПАКТНО (не растягивая).…
Channel created
Showing the 4 most recent of 4 posts we hold for @k_zap. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Куплю Запчасти” (@k_zap), 3,689 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/k_zap.
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.