Telegram RegisterThe public register of Telegram
Telegram profile photo for DKBOTZ

Channel

DKBOTZ

@DKBOTZ

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

1,779subscribers

+81 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001828245581
TypeChannel
Username@DKBOTZ
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/DKBOTZ

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@DK_BOTZ_UPDATES/10275 Aug 2026, 06:50 UTC@DKBOTZ/76 · this entry5 Aug 2026, 06:52 UTC1.002 minutes
@DK_BOTZ_UPDATES/10286 Aug 2026, 00:37 UTC@DKBOTZ/77 · this entry6 Aug 2026, 00:38 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@DK_BOTZ_UPDATES5 (5/5 hand-verifiable sample passed)1.002 minutes@DK_BOTZ_UPDATES (5–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 15 February 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @DK_BOTZ_UPDATES. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,6981,7791,738.57 August 2026 — 1,698 subscribers8 August 2026 — 1,698 subscribers14 August 2026 — 1,708 subscribers17 August 2026 — 1,705 subscribers21 August 2026 — 1,704 subscribers24 August 2026 — 1,707 subscribers28 August 2026 — 1,710 subscribers31 August 2026 — 1,719 subscribers3 September 2026 — 1,717 subscribers9 September 2026 — 1,723 subscribers13 September 2026 — 1,735 subscribers17 September 2026 — 1,745 subscribers27 September 2026 — 1,760 subscribers5 October 2026 — 1,774 subscribers12 October 2026 — 1,779 subscribers7 August 202612 October 2026
15 measurements spanning 65 days, net +81. 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 1,686–1,791 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 01:421,779+5
5 Oct 2026, 13:161,774+14
27 Sept 2026, 06:361,760+15
17 Sept 2026, 16:381,745+10
13 Sept 2026, 11:001,735+12
9 Sept 2026, 14:011,723+6
3 Sept 2026, 22:381,717-2
31 Aug 2026, 13:371,719+9
28 Aug 2026, 03:251,710+3
24 Aug 2026, 23:351,707+3
21 Aug 2026, 00:231,704-1
17 Aug 2026, 15:191,705-3
14 Aug 2026, 15:591,708+10
8 Aug 2026, 04:541,698no change
7 Aug 2026, 16:171,698first reading

Engagement

20 posts held, back to 15 February 2026 — 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

41 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 63.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2663.4%
🎉614.6%
🔥37.32%
🥰37.32%
👍12.44%
😱12.44%
🤩12.44%

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 13 of the 20 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 15 February 2026 to 6 August 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

6 Aug 2026, 00:38 UTC88 viewsread 7 August 2026

🎬 Movies Database Available 🛍 Price: ₹300 For 1 Lakh Movies 💰 Dollar: 4$ For 1 Lakh Movies ✨ Includes: ➡️ New And Old Movies ➡️ Web Series ➡️ Anime ➡️ And Much More 📥 All Content Will Be Sent Directly To Your Private Channel. ✉️ Only Interested Persons Contact Me: @DKBOTZHELP_4

5 Aug 2026, 06:52 UTC121 views1 reactionsread 7 August 2026

😉 ZEE5 API Access Available For Developers 🛍 Pricing 🛍 ➡️ ₹49/Monthly ➡️ ₹499/1 Year ➡️ ₹999/Lifetime ➡️ ₹9/Trial Access For 3 Day (😂) ✨ Features ➡️ Fast And Stable API ✅ ➡️ High-Speed Response ✅ ➡️ Regular Bug Fixes ✅ ➡️ Developer Friendly ✅ 💳 Payment Methods: UPI, USDT (TRC20, BEP20 etc), BTC, And All Cryptocurrencies Are Supported. 📩 Contact For Purchase: @DKBOTZHELP_4

🎉1

3 Aug 2026, 07:01 UTC133 views6 reactionsread 7 August 2026
Forwarded from @DK_BOTZ_UPDATES

📣 Project Update 📣 🕷 All Bugs In @M3U8_MPD_Downloader_Bot Have Been Fixed, And The Latest Version Is Now Working Properly.✅ ⏸ Development For New Updates On @M3U8_MPD_Downloader_Bot Is Being Paused For Now.✅ 😍 @Zee5_Downloader_D_Bot, @Epicon_Downloader_Bot And @MX_Player_Downloader_Bot Are Also Working Properly. They Have Been Designed To Support Future OTT Platforms As Well.✅ ⚠️ If You Find Any Bugs Or Issues, P…

❤6

1 Aug 2026, 11:52 UTC164 views1 reactionsread 7 August 2026
Forwarded from @DK_BOTZ_UPDATES

🚀 New Bot Launched 🎬 @Zee5_Downloader_D_Bot ✅ ✨ Features: ➡️ Download Free Content ➡️ Download Premium Content(Some Premium Content) ➡️ Fast Download Speed ➡️ Easy To Use Interface ⚠️ Found Any Bugs Or Issues? Report Them Immediately. 🤖 𝐌𝐚𝐝𝐞 𝐁𝐲 𝐃𝐊𝐁𝐎𝐓𝐙✅

🔥1

1 Aug 2026, 11:52 UTC176 views1 reactionsread 7 August 2026
Forwarded from @DK_BOTZ_UPDATES

🚀 New Bot Launched 🎬 @Epicon_Downloader_Bot ✅ ✨ Features: ➡️ Download Free Content ➡️ Download Premium Content ➡️ Fast Download Speed ➡️ Easy To Use Interface ⚠️ Found Any Bugs Or Issues? Report Them Immediately. 🤖 𝐌𝐚𝐝𝐞 𝐁𝐲 𝐃𝐊𝐁𝐎𝐓𝐙✅

🔥1

7 Jul 2026, 08:36 UTC492 views6 reactionsread 7 August 2026

🎬 @MX_Player_Downloader_Bot ✨ Version 1.8 📥 A Simple And Powerful MX Player Video Link Generator Bot Is Now Live! Send A Supported MX Player Video Link And Get The Video Details Along With The Download URL Instantly. 🔥 Bot Features 🔗 Generate Direct Download Links 🎬 Automatically Fetch Video Title 📝 Automatically Fetch Video Description ⚡️ Fast Link Processing 📥 One-Click Download Option 🔄 Connected With @M3U8_M…

🎉5🥰1

28 Jun 2026, 12:50 UTC548 views5 reactionsread 7 August 2026

🚀 @File_To_Link_D_Bot Is Now Live! 🎉 We Are Excited To Announce The Biggest Update Ever For @File_To_Link_D_Bot. This Version Has Been Completely Rewritten From Scratch To Deliver Better Performance, A Modern Interface, And Many Powerful New Features. ✨ What's New 🛠 Complete Code Rewrite The Entire Bot Has Been Rebuilt For Better Speed, Stability, And Future Updates. 🎨 Brand New Stream Player A Completely Redesi…

❤4🔥1

28 Jun 2026, 10:56 UTC381 viewsread 7 August 2026

🚀 @GitHub_Uploader_Bot V2 Is Now Live! 🎉 We Are Excited To Announce The Release Of GitHub Uploader Bot V2 With A Faster, Smarter, And More Powerful Uploading Experience. Upload Your ZIP Files Directly To Your GitHub Repository In Just A Few Taps. ✨ What's New In V2 🔑 Multi Token Support Store And Manage Up To 10 GitHub Tokens In One Place. 🔄 Auto Token Rotation The Bot Automatically Switches To Another Token Whe…

9 May 2026, 07:34 UTC984 views7 reactionsread 7 August 2026

🚀 @Youtube_DownloaderProXBot Is Now Live! 🎬 We Are Happy To Announce That @Youtube_DownloaderProXBot Has Been Successfully Launched. This Bot Helps You Download YouTube Videos Quickly And Easily On Telegram. ⭐️ Main Features: 📥 Easy YouTube Download – Download Videos By Simply Sending A YouTube Link. 🎵 Audio & Video Support – Download Both Audio And Video Formats Easily. 📝 Subtitle & Transcript Download – Downlo…

❤5🥰2

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

7 Apr 2026, 08:16 UTCFinal Results42 voters

Do You Want V2 Update Of MX Player Downloader Bot. 💎 Feature: 📤 Direct Video Upload Option 🛫 Quality Selection Option 🎵 Audio Selection Option 🛡 Multi Audio Option (If Available)

  1. 🔠🔠🔠95%
  2. 🔠🔠5%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

3 Apr 2026, 02:53 UTCFinal Results35 voters

⭐️ Are You All Ready For A New Bot? 🐋 💍 MX Player Downloader Bot ✅

  1. 🔠🔠🔠86%
  2. 🔠🔠14%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 15 February 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

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.

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

“DKBOTZ” (@DKBOTZ), 1,779 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/DKBOTZ.

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.