Channel
@degendenn
On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,169subscribers
+707 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001888557913 |
|---|---|
| Type | Channel |
| Username | @degendenn |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/degendenn |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 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 the other topics.
@degendenn was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 02:51 | 4,169 | -6 |
| 1 Nov 2026, 04:50 | 4,175 | -10 |
| 29 Oct 2026, 12:00 | 4,185 | -16 |
| 26 Oct 2026, 01:07 | 4,201 | -8 |
| 22 Oct 2026, 21:51 | 4,209 | -7 |
| 20 Oct 2026, 04:59 | 4,216 | +21 |
| 17 Oct 2026, 10:29 | 4,195 | -15 |
| 14 Oct 2026, 05:39 | 4,210 | +48 |
| 10 Oct 2026, 16:02 | 4,162 | +335 |
| 4 Oct 2026, 18:37 | 3,827 | -37 |
| 25 Sept 2026, 00:37 | 3,864 | +16 |
| 16 Sept 2026, 19:18 | 3,848 | +139 |
| 15 Sept 2026, 12:22 | 3,709 | no change |
| 15 Sept 2026, 11:47 | 3,709 | +285 |
| 12 Sept 2026, 05:36 | 3,424 | -18 |
| 7 Sept 2026, 14:02 | 3,442 | -10 |
| 2 Sept 2026, 06:53 | 3,452 | -7 |
| 30 Aug 2026, 14:53 | 3,459 | -3 |
| 29 Aug 2026, 21:15 | 3,462 | first reading |
32 posts held, back to 31 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 32 posts for this entry, the most recent from 15 September 2026. An engagement rate over an empty window would be a number about nothing.
106 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 52.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 56 | 52.8% | |
| 🔥 | 37 | 34.9% | |
| 👍 | 13 | 12.3% |
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 21 of the 32 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 106 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 31 March 2025 to 15 September 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.
0xc466c28d87b3d5cd34f3d5c088751532d71a38d93a8aae4551dd56272cfb4355::manifest::MANIFEST $manifest is a solid meme on sui and i have seen the founder supporting the project indirectly so i feel when the sui trench starts running, this will go to millions
❤7
Just got off call with wifey only to come online and see people selling at 26k😂 Anyways its better you to take peanuts than lose money More to come guys we gon print heavily 😍😍
❤8
Sent at 20k Lets see how far this can go Always know when to take profits and maximize your risk Lfg
🔥8❤2
Lfg
0xf631f902e31d96fa8fcb37a68a0ed6aa6d28ebb4afc5a3178365aff704a1e8bf::storm::STORM
❤3
Use this bot
Sui call dropping
👍2
Fund your sui bot Dropping calls soon
❤9👍1
React if you’re active
🔥23❤15👍4
Bot use for other chain: https://t.me/based_eth_bot?start=r_979329053
Bot i use for sui memes: https://t.me/suistrikebot?start=ref_979329053 Its fast and smooth
Will be dropping some solid degen calls in this channel while we keep the main channel for airdrop and futures trading Everything airdrop and futures trading please join this: https://t.me/wilson_space But if you want to trade memecoins too you can stay here
❤1
Showing the 12 most recent of 32 posts we hold for @degendenn. 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.
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.
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.
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.
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Degen Den💰” (@degendenn), 4,169 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/degendenn.
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.