Channel
@themaddev
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
44subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002083041743 |
|---|---|
| Type | Channel |
| Username | @themaddev |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/themaddev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 15:46 | 44 | no change |
| 7 Aug 2026, 13:12 | 44 | first reading |
20 posts held, back to 19 July 2024 — 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 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 19 September 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
13 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 6 | 46.2% | |
| ❤ | 3 | 23.1% | |
| 👍 | 3 | 23.1% | |
| 😁 | 1 | 7.69% |
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 7 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 13reactions 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 19 July 2024 to 19 September 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Yesterdays launch was our first on meteora and moonshot. Unfortunately Meteora is not set up yet to be successful but its close. It was showing the liquidity pool as holder and giving warnings that %50+ of the tokens were owned by top 10 holders. 5kehwbmzdmykuucnkh6uiwpdqsgtz5cu7ccu7hmz9qff $dirb We were able to bond but unfortunately it went downhill from there. We were able to hold the floor but too many issue…
Recap for the last project: $ RAMEN 9GQws1vXJMk4iYoMbNgS3gW9h2VWFcYot6CQFyCwpump All in all we did good and broke 100k but we aren't shooting for 100k, we are looking for 1 million and I think we will get there. We had some weird snipers that I believe we can shake out this time. Our team will not be happy until we truly moon one.
Better late than never. Recap of our last project. $micropepe 6evp8iZqwXe46Qgt7S17RD68dQr6SZ5KtwRuSjfnpump Our project from two weeks ago bonded and hit 80k market cap. We feel like we can still do a lot better. we will be better preared than last time. We launched on a Fri night with really low volume when Sol was down bad. Next project coming soon.
Joining up with some people tomorrow. We have a great meme, original art, along with a strong team. KOLs have been onboarded, advertising will be paid, and market caps will be climbed. Launch tomorrow around 3pm PST Invite your friends if you'd like https://t.me/SolanaLaunchpadInviteOnly
everyone sell, we got fud caballed, we wont dump on you its just stupid to try and continue
$ded ☠️☠️☠️ The internet's favorite little baby Orangutan first appeared in 2011 on 4chan and blew up into a meme superstar. https://pump.fun/CJDeC1PQM4bodg8dXTCVQyKoUaZxyrz9B3C5Nq9pump CJDeC1PQM4bodg8dXTCVQyKoUaZxyrz9B3C5Nq9pump twitter: https://x.com/DedCoinOnSol telegram: https://t.me/dedcoinonsol website: https://deadcoin.life/
Ok for real launching soon
👍1
Launching a project in 3hrs
❤1
hey guys im calling it, not sure why this one didnt do well... I guess the meme was overdone? sorry guys we will keep trying. sell so I dont dump on you
👍1😁1
Snoop and his favorite torch at the Paris Olympics. https://pump.fun/EkqF9PGQnJUjgQNRYYkkpmiB43ue1YkWdyTixxFTpump EkqF9PGQnJUjgQNRYYkkpmiB43ue1YkWdyTixxFTpump https://olympicblunt.xyz/ https://t.me/olympicblunt https://x.com/olympicblunt
Should be launching in 30-40ish minutes
🔥2
Guys we figured out why our last launch tanked so hard. There's a bot that immediately takes our coin and buys it up to KOH, it uses all of the same socials. People enter our telegram thinking its a legit project and even participate on voice but they are on the wrong pumpfun page. We had a few people telling us the price wasnt right on the buy bot and we had no idea what was happening. Fucking wild wild west out…
Showing the 12 most recent of 20 posts we hold for @themaddev. 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.
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.
@themaddev named 4 handles 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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Mad Dev” (@themaddev), 44 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/themaddev.
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.