#update @creationdatebot A generous donor has paid to have the bot reinstated. Wohoo! Enjoy.
💩63❤25👏4👍3🍌2👎1

Channel
@devctl
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
4,236subscribers
-26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001251020931 |
|---|---|
| Type | Channel |
| Username | @devctl |
| Created | Between 1 March 2018 and 14 July 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/devctl |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 05:47 | 4,236 | -9 |
| 10 Aug 2026, 12:01 | 4,245 | -17 |
| 6 Aug 2026, 16:00 | 4,262 | no change |
| 6 Aug 2026, 15:59 | 4,262 | first reading |
20 posts held, back to 14 July 2019 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof 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 9 December 2021. An engagement rate over an empty window would be a number about nothing.
160 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 39.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 63 | 39.4% | |
| ❤ | 45 | 28.1% | |
| 🤣 | 27 | 16.9% | |
| 👎 | 7 | 4.38% | |
| 😢 | 6 | 3.75% | |
| 👍 | 4 | 2.50% | |
| 👏 | 4 | 2.50% | |
| 🍌 | 2 | 1.25% | |
| ❤🔥 | 1 | 0.625% | |
| 🔥 | 1 | 0.625% |
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 8 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 160reactions 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 14 July 2019 to 9 December 2021, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#update @creationdatebot A generous donor has paid to have the bot reinstated. Wohoo! Enjoy.
💩63❤25👏4👍3🍌2👎1
#issues @creationdatebot Hi guys. The Creation Date Bot requires a server to function, for which I have for years, till now, now paid out of my own pocket to maintain the free service. I am now a broke college student. The server fee is $5/month. The bot is currently down but if you’d like to support the cost please donate: Bitcoin: bc1qq9tjag6fpsyf9yf36er7vwjdagu69l2kfjqwhp Venmo: @komron
🤣27❤11😢6❤🔥1
#issues @creationdatebot The bot is back online after weeks of downtime. Feel free to use it and sorry for any inconveniences.
#update @creationdatebot Shout out to @hfsoriad for translating the bot to Portuguese, Spanish and @prizrique for the Uzbek translation. They’re already being added to the /credits section.
❤1
#update @creationdatebot For a while now, the source code of Creation Date has been licensed under MIT and been publicly viewable on GitHub. You can go over and check out everything that keeps it running: https://github.com/karipov/creationDate Give some love to the project by starring it 🌟!
❤3👍1
#update @creationdatebot Due to popular demand and some (very) vocal people, the manual /id command is making a comeback! Usage: /id ANYUSERIDHERE
❤2🔥1
#update @creationdatebot Want to give a big shoutout to @kernoeb for helping translate the bot to French. He’s now under the /credits section in the bot. If you would like to contribute to the development and translate the bot to your language, feel free to reach out (REDACTED) Stay tuned ✌️
❤2
#new @tagtrackbot Telegram macOS Swift (@macswift) bug and suggestions tracker; integrates with Trello. source: https://github.com/karipov/tagtrack
Signed vaprio
#issues @creationdatebot The flood issue has been handled. If over-used, you will have to wait to use it. In the future I may be adding more capacity for this function, but as of now the demand isn’t too strong. Stay tuned for more updates!
❤1
Signed vaprio
P.S. regular messages and forwards are still functioning
Signed vaprio
FloodWaitError: A wait of 3033 seconds is required (caused by ResolveUsernameRequest)
Signed vaprio
#issues @creationdatebot Wow! You guys are wild. Currently it appears that telegram has temporarily banned the bot from resolving usernames. In the future, to prevent this, I’m afraid this command will be limited to a certain maximum per day. Meanwhile, I’ll be fixing the issue. Go easy on the bot please!
Signed vaprio
Showing the 12 most recent of 20 posts we hold for @devctl. 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.
@devctl named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“komron’s bots inc.” (@devctl), 4,236 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/devctl.
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.