Channel
@KBDppp
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002051246515 |
|---|---|
| Type | Channel |
| Username | @KBDppp |
| Description | Привет♡ добро пожаловать в логово раз ты зашёл на эту тереторию значит ты член нашего логова ~🍿 Надеюсь тебе здесь понравится☆ День рождение 26 августа😔 я фан милки,ириски...♥︎♥︎♥︎♥︎ я ее сьем ;)> |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KBDppp |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:16 | 10 | no change |
| 7 Aug 2026, 12:53 | 10 | first reading |
9 posts held, back to 21 April 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 9 posts for this entry, the most recent from 15 May 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
Measured directly from 8 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.
—Было что-то похожее на мини сходку) На фото не моя маска(!) -есть друзья квд? Вчера отправила заказик=∆ -Что лучше заказать, хвост или митенки? Все хвостики и маски на видео мои=3 (возможно возьму рест по постам) 〰️〰️〰️〰️〰️〰️〰️ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
—Заказик<3 Видосы с маской на заказ хех, она ещё не готова! -продавали маски? Мне нравится прыжок, однако толчок нужно улучшить... У меня и так с качеством плохо, а тг решил его доесть =< (Хотела выложить давно =3) 〰️〰️〰️〰️〰️〰️〰️ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
—Гуляла с сестрой у нас в деревне =) -мне понравилось 2 видео ;) -делали когда-нибудь маску на заказ? У этой мистической кошки много хвостиков •^• 〰〰〰〰〰〰〰 ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
—Начинается новая эпоха Дракоши!) -Теперь я по другому стану оформлять свой канальчег =3 -Как вам видосики? В школе было стрёмно снимать °^° 〰〰〰〰〰〰〰 ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
Извините, у меня не отправился пост [я его написала 1 мая] :(( #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
°вот вам старенькое видео° ✮ ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ • с 1 мая вас!! • начался май... Сейчас буду потихоньку менять некоторые вещи в постах ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ Теге: тык ✮ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
°1 видео мне не нрав =<° ✮ ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ • отписки... • скоро я изменю оформление постов и другое ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ Теге: тык ✮ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
°вай =∆° ✮ ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ • извините за отсутствие(( •ничего не могу поделать с качеством... • напишите в коммы задания по типу "перепрыгни подушку" и похожее ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ Теге: тык ✮ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
°завал фото с видосами :3° ✮ ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ • сегодня приехала домой... • #Чайка2025 дооо ⋅•⋅⊰∙∘☽༓☾∘∙⊱⋅•⋅ Теге: тык ✮ Ваша #ᴅʀᴀᴋᴏsʜᴀ
Signed -; я ᴛʏᴛ ✨ᴰʳᵃᵏᵒˢʰᵃ✨ ;- #афёнок #лолофд #тери)
Showing the 9 most recent of 9 posts we hold for @KBDppp. 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“🌾🍃 Норка Мейкуна🍃🌾” (@KBDppp), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/KBDppp.
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.