Telegram RegisterThe public register of Telegram

Channel

Bots.DC

@dcbots

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

147subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001414658251
TypeChannel
Username@dcbots
DescriptionBots created by @dcdunkan. See the pinned message for the list of the bots and more information.
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/dcbots

Growth

1476 August 2026 — 147 subscribers8 August 2026 — 147 subscribers6 August 20268 August 2026
2 measurements spanning 2 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 146–148 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 20:31147no change
6 Aug 2026, 22:39147first reading

Engagement

20 posts held, back to 2 October 2021the 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 20 posts for this entry, the most recent from 6 September 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Links
23

Lifetime counters from Telegram’s own channel header, read 8 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

79 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 31.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2531.6%
1316.5%
🔥1113.9%
🐳911.4%
💩911.4%
🎉45.06%
👏33.80%
22.53%
🤡22.53%
🏆11.27%

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 12 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 79reactions 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 2 October 2021 to 6 September 2022, 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 Sept 2022, 07:38 UTC≈3,520 views11 reactionsread 8 August 2026

Updated Slash Report Bot (@ryportbot)! • Fixed issue with reporting users sending messages as channels. • Removed "Ban" and "Ignore" buttons (admins should be taking required actions by themselves—manually). • Deletes the message containing admin mentions after an admin click "Handled". • No longer mention about the reporter in the message.

👍621🏆1💩1

Signed Dunkan

25 Aug 2022, 13:46 UTC≈3,560 views6 reactionsread 8 August 2026

Rate Slash Report (@ryportbot) at BotsArchive here: https://t.me/BotsArchive/2500. Thanks in advance for the votes!

👍5🤡1

Signed Dunkan

18 Aug 2022, 11:35 UTC≈3,460 views8 reactionsread 8 August 2026

New update! Slash Report Bot (@ryportbot) • Added proper support for reporting users sending messages as their public channels. • Ignores /reports of Linked Channel posts. • Everything in one message! • Added shortcuts buttons for Banning reported user, Marking the report as Handled, and Ignoring it. After admins take an action, bot removes the mentions and updates the report message about the action (Only shows ban

🎉4🐳2👍1💩1

Signed Dunkan

14 Aug 2022, 19:00 UTC≈2,540 views10 reactionsread 8 August 2026

A tiny update! 🎨 Syntax Highlighter v0.5.0 (@syntaxybot) No longer uses puppeteer screenshot magic to render syntax highlighted images. Bot has become more faster and now gives you better highlighted images. It uses a custom HTML to SVG script then (thanks to svg2png-wasm) converts the SVG to PNG. See the updated source (core) for more details. Since it no longer uses puppeteer for rendering, and uses a solution th

🐳52🔥2💩1

Signed Dunkan

28 Jul 2022, 05:58 UTC≈1,690 views11 reactionsread 8 August 2026
Photo

a new bot! Slash Report Bot (@ryportbot) Simple time-aware report bot. It listens for /report, /admin commands or @admin, @admins mentions in groups, and mentions all admins. Admins can set their timezone and unavailability time period in the bot's PM and only receive mentions when they are available. Send /help for help. Add bot to your group » Source: https://github.com/dcdunkan/ryportbot Built with grammY. Depl

👍7👏3💩1

Signed Dunkan

15 Jun 2022, 11:06 UTC≈1,500 views9 reactionsread 8 August 2026

Changelogs 0.x of Syntax Highlighter Bot (@syntaxybot) ✨ #4: Move to Shiki could be the next one! Subscribe to get notified when the update is released! # 0.5.0 The no puppeteer + Deno Deploy update! ⚡️ Update details: https://t.me/dcbots/62 # 0.4.0 Using any of w, no-wrap, nw as an argument for the /highlight command can now highlight the message without wrapping the code. Useful if you're sharing some terminal o

👍6🐳2💩1

Signed Dunkan

30 May 2022, 16:58 UTC≈1,260 views1 reactionsread 8 August 2026

Edit: Up again! Heroku free dynos ran out. So, @syntaxybot is down. Restarts on: June 1

💩1

Signed Dunkan

12 May 2022, 14:48 UTC≈1,400 views11 reactionsread 8 August 2026

https://t.me/BotsArchive/2403 Thank you for all of your ratings :) ...and we got the 🥈 2nd Best Bot of the Week, with a rating of 4/5 in 66 votes 😎 https://t.me/BotsArchive/2407 🎉 100 subscribers on May 13, 2022 Thank you all for supporting the channel

🔥91💩1

Signed Dunkan

12 May 2022, 14:48 UTC≈1,220 views1 reactionsread 8 August 2026
Forwarded from @BotsArchive

🤖 New bot 📋 Name: Syntax Highlighter 🆔 Username: @syntaxybot ⭐️ Rating: ⭐️⭐️⭐️ (3.6/5 on 28 votes) ➖➖➖ ℹ️Description: A bot to syntax highlight code blocks in chats. Ability to customize theme and font. Useful for developer group chats. 🌐 Languages: English 💬 Supports inline: no 👥 Groups: yes #️⃣ Tags: #syntax #highlight #developers #code

🤡1

Signed Dunkan

20 Apr 2022, 09:09 UTC≈1,390 views7 reactionsread 8 August 2026

🎈 A new bot (edition)! Experimental WebApp edition (beta) of the previous bot Syntaxy2.0 (@syntaxyybot) What this bot can do? Basically the same as the above one. It can syntax highlight the code blocks in messages. But this does not have many features as the previous one do. So, what is the experiment? It shows you the syntax highlighted previews in a web app. It uses features from the latest Telegram update to sh

6💩1

Signed Dunkan

16 Apr 2022, 08:23 UTC≈1,150 views1 reactionsread 8 August 2026
Photo

🎉 New bot! Syntax Highlighter Bot (@syntaxybot) > Update Changelogs > Experimental Edition This bot can syntax highlight code blocks in messages. Can be used in private and group chats. Useful in Developer group chats. Add to group » Theme and font can be customized. Use the /as_doc command to toggle "Send as Document" mode to overcome the Telegram compression. Reply /highlight to a message to force highlighting.

💩1

Signed Dunkan

23 Feb 2022, 14:10 UTC999 views3 reactionsread 8 August 2026
Photo

🎉 Scripture Bot v4 (@scripturbot) An update with few improvements and new features, introducing Bookmarks, Settings, Go to last read and some UI improvements. Completely re-wrote the version 3, which was written in Telegraf-NodeJS-JavaScript, to version 4, which is written in grammY-Deno-TypeScript. The bot is currently hosted on Deno Deploy (Beta: Free). The bot is way faster than the previous version. And, let's h

3

Signed Dunkan

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

Citation-graph rank

Citation-graph rank — 900,052 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Bots.DC” (@dcbots), 147 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dcbots.

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.