Telegram RegisterThe public register of Telegram
Telegram profile photo for The Dude ™👨‍💼

Channel

The Dude ™👨‍💼

@thedude0ne

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

6,598subscribers

-78 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001127224009
TypeChannel
Username@thedude0ne
Created29 August 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/thedude0ne

Topic

Crypto & trading — 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 96% 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@thedude0ne/18546 · this entry6 Aug 2026, 08:24 UTC@CryptoDegensClub/23476 Aug 2026, 08:25 UTC1.00under a minute
@thedude0ne/18548 · this entry6 Aug 2026, 12:46 UTC@CryptoDegensClub/23496 Aug 2026, 12:46 UTC1.00under a minute
@thedude0ne/18552 · this entry6 Aug 2026, 13:31 UTC@CryptoDegensClub/23516 Aug 2026, 13:41 UTC1.0011 minutes
@thedude0ne/18556 · this entry6 Aug 2026, 16:54 UTC@CryptoDegensClub/23556 Aug 2026, 16:55 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@CryptoDegensClub9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (90)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 27 July 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 @thedude0ne — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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

6,5986,6766,6376 August 2026 — 6,676 subscribers6 August 2026 — 6,676 subscribers9 August 2026 — 6,660 subscribers12 August 2026 — 6,651 subscribers16 August 2026 — 6,646 subscribers19 August 2026 — 6,639 subscribers22 August 2026 — 6,635 subscribers25 August 2026 — 6,623 subscribers28 August 2026 — 6,618 subscribers31 August 2026 — 6,626 subscribers3 September 2026 — 6,624 subscribers9 September 2026 — 6,613 subscribers12 September 2026 — 6,607 subscribers16 September 2026 — 6,598 subscribers6 August 202616 September 2026
14 measurements spanning 42 days, net -78. 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 6,586–6,688 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 15:006,598-9
12 Sept 2026, 23:576,607-6
9 Sept 2026, 03:146,613-11
3 Sept 2026, 17:426,624-2
31 Aug 2026, 13:446,626+8
28 Aug 2026, 11:536,618-5
25 Aug 2026, 16:166,623-12
22 Aug 2026, 13:586,635-4
19 Aug 2026, 15:036,639-7
16 Aug 2026, 17:146,646-5
12 Aug 2026, 22:576,651-9
9 Aug 2026, 14:166,660-16
6 Aug 2026, 03:186,676no change
6 Aug 2026, 02:276,676first reading

Engagement

64 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pages 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 64 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

218 reactions across 41 posts, in 5 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11050.5%
🔥9443.1%
👍94.13%
🎉41.83%
👌10.459%

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

Measured over the 64 most recent posts we hold, published 27 July 2026 to 19 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

19 Aug 2026, 21:29 UTC258 views5 reactionsread 20 August 2026

$BTC flying! Another bull run is starting! Are you ready?!

5

18 Aug 2026, 17:50 UTC321 views21 reactionsread 20 August 2026

GMGM I have been achieving incredible results with the tools guiding some of our calls here. The future will be very bright for us! I expect to share more and more high-level content over the next months. Are you ready?!🔥

21

16 Aug 2026, 21:27 UTC483 views5 reactionsread 20 August 2026
Photo

I dare you to find me a better chart!

🔥4🎉1

16 Aug 2026, 21:12 UTC384 views5 reactionsread 20 August 2026

In a tough market like this, finding a coin that you can buy, hold, and work with is extremely hard, and that's $WOJAK right now. I don't see any other one atm.

5

13 Aug 2026, 20:22 UTC502 views6 reactionsread 20 August 2026

There are some fake rumors that I'm launching a coin today. I'm not launching anything (at least not today). Be careful with scammers. When I actually do something, you will always hear from me here.

6

11 Aug 2026, 23:41 UTC493 views8 reactionsread 20 August 2026
Photo

You did it! 50 likes was easy. See how much you can achieve when you focus? You deserve this next move 🔥🪙

🔥8

11 Aug 2026, 22:02 UTCviews —

The Dude ™👨‍💼 pinned «https://dexscreener.com/robinhood/0xD43499Bbe3150f7e888a0C5F08d6214C34E38fd2 Heard by very good sources that this is being grounded by top players in the space. The chart looks really good and organic, and it has been live for a few days. It is probably the…»

11 Aug 2026, 22:01 UTCviews —

The Dude ™👨‍💼 pinned «The alpha I received on $WOJAK was from the same source that sent me $GIGACHAD (on Solana) at $10 million before it hit $900 million. After over two years, he sent me this second coin. Take that info as you want. Just remember that I posted it here around…»

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

11 Aug 2026, 06:06 UTCAnonymous Poll42 voters

$WOJAK smashing ATH everyday! But are you holding? Let's see how early we are!

  1. WORKING FOR MY BAG EVERYDAY 🔥36%
  2. NOT IN 😪55%
  3. BUYING NOW!!10%

Shares as published, totalling 101%. 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 64 most recent posts we hold, published 27 July 2026 to 19 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 registered channels — 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Klondike (Crypto Rush) ⚠️
@CryptoKlondike · 59,571
Telegram ranks this channel #11 of 77 here — alongside 76 others — read 22 August 2026
Lumia News
@lumia_news · 105,871
Telegram ranks this channel #20 of 87 here — alongside 86 others — read 15 August 2026
Crypto Daku
@cryptodakuofficial · 50,100
Telegram ranks this channel #36 of 95 here — alongside 94 others — read 25 August 2026
JustTopIco
@JustTopico · 33,544
Telegram ranks this channel #37 of 85 here — alongside 84 others — read 3 September 2026
D Man
@blockchainwhispersbaby · 99,497
Telegram ranks this channel #39 of 91 here — alongside 90 others — read 15 August 2026
CryptoBullet
@cryptobullet · 67,275
Telegram ranks this channel #54 of 77 here — alongside 76 others — read 20 August 2026
ICO Drops - ICO News & Alerts
@icodrops · 42,846
Telegram ranks this channel #56 of 87 here — alongside 86 others — read 28 August 2026
Rocket Wallet Signals
@RocketWallet_Official · 23,465
Telegram ranks this channel #57 of 72 here — alongside 71 others — read 18 September 2026
Kim & Crypto
@kimoncrypto · 37,722
Telegram ranks this channel #59 of 75 here — alongside 74 others — read 31 August 2026
CryptoDiffer News
@cryptodiffer · 23,613
Telegram ranks this channel #67 of 89 here — alongside 88 others — read 18 September 2026
CCC.io
@cccio · 33,830
Telegram ranks this channel #71 of 85 here — alongside 84 others — read 3 September 2026

This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“The Dude ™👨‍💼” (@thedude0ne), 6,598 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/thedude0ne.

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.