Telegram RegisterThe public register of Telegram
Telegram profile photo for вп + реклама.❗

Channel

вп + реклама.❗

@dkbkmizu

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

6subscribers

+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-1002319435900
TypeChannel
Username@dkbkmizu
DescriptionДЛЯ ПРИОБРЕТЕНИЯ РЕКЛАМЫ ПИШИТЕ — @dkbku
CreatedBetween 1 September 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 September 2026
Measurements held2
On Telegramt.me/dkbkmizu

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:456no change
7 Aug 2026, 18:456first reading

Engagement

7 posts held, back to 30 September 2024the 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 19 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
17
Links
3

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.

Reaction mix

6 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤯466.7%
233.3%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 5 of the 7 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 30 September 2024 to 19 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

19 Feb 2026, 14:35 UTC21 views1 reactionsread 12 August 2026
Forwarded from @BKDK20_15Photo

2. Случай, когда Алекс наебали. Алекс, не злись. Это в благих намерениях.

🤯1

19 Feb 2026, 14:35 UTC21 views1 reactionsread 12 August 2026
Forwarded from @BKDK20_15Photo

1. Случай с Мизу. Мизу, солнце, не злись. Очень хочу уберечь владельцев от этой гниды.

🤯1

19 Feb 2026, 14:35 UTC17 views1 reactionsread 12 August 2026
Forwarded from @BKDK20_15

4. Мне пришлось лично с ним списаться с ультиматумом о том, что я выкупаю этот канал. В случае нас с Мизу всё получилось, как вы знаете. Я успешно купил канал, продолжают его вести и нас никто не беспокоит. Но есть второй случай, там владельцу повезло меньше всех. Бывший влд домика бкдк @Yuitsuu была обманута этим самым челом. Я давненько интересовался, что случилось с каналом, и до меня дошли сведения, что она влд

🤯1

19 Feb 2026, 14:35 UTC14 views1 reactionsread 12 August 2026
Forwarded from @BKDK20_15Photo

— хуета, короче. Делаю объявление и обращение, уже не первый случай замечен. — обращение ОСОБЕННО К ВЛАДЕЛЬЦАМ каналов с мга и шипом бкдк: если увидите данную персону на своём тгк или он вам напишет с целью «помочь», или вы решите продать свой тгк НИ В КОЕМ СЛУЧАЕ не отвечайте ему и удалите со своего тгк. — зафиксировано как минимум 2 случая связанных с этим человеком. Лично я столкнулся с ним, когда Мизу продавал св

🤯1

12 Jan 2026, 17:36 UTC201 viewsread 12 August 2026

· · ─────── ·𖥸· ─────── · · ​​ ❝ ДОБРО ПОЖАЛОВАТЬ НА КАНАЛ NUMBER ONE!😄 🤩 :; у нас разнообразный контент! ───── — зарисовки! — делаем классные премиум эмодзи и обычные стикеры! — красивые эдиты с нашими любимыми КацуДеку! — аушки, хендканоны и идеи для ваших зарисовок или даже фф! ───── → С НЕТЕРПЕНИЕМ ЖДЁМ ВАС В НАШЕМ КАНАЛЕ! ← · · ─────── ·𖥸· ─────── ·

11 Apr 2025, 09:11 UTCviews —

вп + реклама.❗ pinned «❗️вп делаю только по каналам связанным с аниме тематикой. • на вашем канале, должно быть хотя бы 50 - 100 подписчиков. ‼️‼️‼️ Я НЕ ДЕЛАЮ ВП С КАНАЛАМИ, КОТОРЫЕ НЕ ОТМЕЧАЮТ ХУДОЖНИКОВ. ‼️‼️‼️»

30 Sept 2024, 05:14 UTC≈18,900 views2 reactionsread 12 August 2026
Photo

🤩 — ДОБРО ПОЖАЛОВАТЬ, НА КАНАЛ ПО БКДКБК!🐾 🤩 — у нас есть: • зарисовки. • арты по бкдкбк! • по вашим просьбам делаем прем. стикеры / стикеры! • день для показа ваших артов. ✨ • идеи для ваших мини-фф/фф. →→ ЖДЁМ ВАС НА СВОЁМ КАНАЛЕ! 👾 ←←

2

Showing the 7 most recent of 7 posts we hold for @dkbkmizu. 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.

Mentions

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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“вп + реклама.❗” (@dkbkmizu), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dkbkmizu.

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.