Channel
@The_Dag_0
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
122subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003925700310 |
|---|---|
| Type | Channel |
| Username | @The_Dag_0 |
| Created | Between 1 April 2026 and 27 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/The_Dag_0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 20:57 | 122 | +1 |
| 23 Aug 2026, 15:24 | 121 | -2 |
| 9 Aug 2026, 03:17 | 123 | no change |
| 7 Aug 2026, 20:03 | 123 | first reading |
20 posts held, back to 27 June 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
48 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 35.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 35.4% | |
| 🤣 | 9 | 18.8% | |
| 😁 | 6 | 12.5% | |
| 🔥 | 4 | 8.33% | |
| 😭 | 4 | 8.33% | |
| 🙊 | 3 | 6.25% | |
| 🫡 | 3 | 6.25% | |
| 👍 | 1 | 2.08% | |
| 🥰 | 1 | 2.08% |
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 14 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 48 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 27 June 2026 to 5 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.
A couple of weeks ago, I said: I wish there was a Linktree for bank accounts. 8 people said they'd use it. So naturally, I built it. 😅 PayLink is now live 🚀 One page for all your bank accounts and payment methods. No signup required. You can try it out in seconds. 🌐 https://paylink-et.vercel.app Feedback is welcome! 👀
🔥3
As a developer, UI/UX design has never been my strongest skill. That's why I've been using Google's Stitch quite a bit lately. Whenever I have an idea for a website, I describe it, generate a few designs, and use them as inspiration before recreating and refining them in actual code. It's not replacing designers anytime soon, but it's amazing for exploring ideas quickly. Definitely one of the AI tools that's made…
❤1👍1🔥1
fkn demo today at 10am, last night 2-3 hr sleep and we are at work again @bugpusher
Built a tiny niche app for a problem that probably only I have. 😅 I got tired of manually forwarding SMS messages from one phone to another, so instead of finding a workaround, I spent hours building an app. Classic developer behavior. Will anyone else use it? Probably not. Did I enjoy building it? Absolutely. 🚀 Source code: https://github.com/DagNo1/SMSForwarder
❤2
Photo, posted without a caption
Should I quit programming and stay out here🤔
How the time flies by😳
▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░ ፹፭% (85%)
Service charge of 129 birr for a small transaction is robbery😭😭 Screw you CBE
🙊3
Would you use this? 👀
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Trying to remember which bank account to send people is becoming annoying. Every time someone asks for payment details, I end up digging through old messages looking for the right account. And I don't want to use Telegram Saved Messages. Mine is already full of random stuff. 😅 I wish there was a Linktree, but for bank accounts. One link. All your payment methods. 🤔
❤1
The type of shit I deal with when I tell codex to implement a feature I designed
😁4
Showing the 12 most recent of 20 posts we hold for @The_Dag_0. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Would you use this? 👀
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 27 June 2026 to 5 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.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“The Dag” (@The_Dag_0), 122 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/The_Dag_0.
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.