Crypto SuperCycle 0x113f9616AD86A358bB7e58EB3E977D976aF44444 https://dexscreener.com/bsc/0x459b2319c85afad8058eafa199012126b3d4de32 https://x.com/makassescrew/status/1999481559569846672?s=46&t=LYdsSDzrYYtvrMpdv9e7Pw

Channel
makasse's crew
@makassescrew
On this record: Topic · Growth · Engagement · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
1,703subscribers
-132 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001554419128 |
|---|---|
| Type | Channel |
| Username | @makassescrew |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/makassescrew |
Topic
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 21:18 | 1,703 | -8 |
| 12 Sept 2026, 20:36 | 1,711 | -18 |
| 8 Sept 2026, 18:37 | 1,729 | -11 |
| 3 Sept 2026, 12:21 | 1,740 | -10 |
| 31 Aug 2026, 04:55 | 1,750 | -16 |
| 27 Aug 2026, 19:54 | 1,766 | -8 |
| 24 Aug 2026, 11:19 | 1,774 | -11 |
| 20 Aug 2026, 20:33 | 1,785 | -12 |
| 17 Aug 2026, 11:17 | 1,797 | -7 |
| 14 Aug 2026, 05:58 | 1,804 | -9 |
| 11 Aug 2026, 03:42 | 1,813 | -14 |
| 7 Aug 2026, 23:46 | 1,827 | -8 |
| 7 Aug 2026, 04:16 | 1,835 | no change |
| 7 Aug 2026, 04:07 | 1,835 | first reading |
Engagement
20 posts held, back to 13 October 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 20 posts for this entry, the most recent from 12 December 2025. An engagement rate over an empty window would be a number about nothing.
Telegram Stars
- Stars received
- 32
- across the posts below
- Posts paid on
- 9
- of 20 we hold a reading for · 45%
- Most on one post
- 7
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @makassescrew. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 13 October 2025 to 12 December 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
https://x.com/makassescrew/status/1999237287440163101?s=46&t=LYdsSDzrYYtvrMpdv9e7Pw
CyberBucks $CB CyberBucks was the first form of digital money, created in the 1990s as a practical implementation of David Chaum’s 1982 eCash concept, long before today’s digital currencies emerged. 9o4P6SeJ386nzfxfB163TiX4xVPmLb7LMGWDAjR9pump https://dexscreener.com/solana/abxvw7hkaxsfqtnwn9cqctb2crpvvfkefkrxge6rs44c https://cyberbucks.live/ https://x.com/i/communities/1999216274296176709
Achievement Unlocked: x3! ☝️ @makassescrew made a x3+ call on NPC. $749K ➡️ $2.3M 👁 View Call 📊 View Stats ➡️Auto-buy and sell calls like this through SpyDefi Filters!
Achievement Unlocked: Conviction! 👩🎓 @makassescrew had the conviction to call NPC at a higher marketcap and it just hit x2+. $749K ➡️ $1.6M 👁 View Call 📊 View Stats 🔸 STABLE - TRENDING #1
Photo, posted without a caption
Gnomed i like this, lets see EG1dKNkpjWF5re9t9d7MoxRmGd8gzjpBDpbb4oiZpump https://pump.fun/EG1dKNkpjWF5re9t9d7MoxRmGd8gzjpBDpbb4oiZpump
everything feels 10x cheaper when you convert it to sol
$NPC Looking for an entry here, the ONLY $NPC meme with officially registered IP in the European Union. All licenses + legal info are on the website. Past tokens/memes with the IP did pretty good before so yh I'll DCA and build a position. DYOR. Trademark: https://euipo.europa.eu/eSearch/#details/trademarks/019284341 IP Design: https://euipo.europa.eu/eSearch/#basic/1+1+1+1/019284341 GdKWebBBvM78HNYGxoZLgsXHqZKAEL…
JUST IN: $3,400 $ETH @WatcherGuru
PCGAMEFI 💰 PC GameFi is building the next generation launchpad for high-quality gaming projects. Our platform combines AI-powered analytics, fair allocation systems, and sustainable tokenomics to deliver unmatched value to our community. https://www.pinksale.finance/launchpad/ethereum/0x5b4dD25CB3B70A78578C9611C5685Bb081c193c3 https://t.me/PCgamefi https://x.com/pcgamefi https://www.pcgamefi.net/
nanoGPT 26deXuNqX8U8cNUy619JXkgRpRhXV2vkwQui9rJ3pump https://dexscreener.com/solana/37JKrAcWty7RqKRaWMwMUbkaneF6fJRVzAS4aTrC8gXf
Showing the 12 most recent of 20 posts we hold for @makassescrew. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@makassescrew 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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.
@topresale · 85,951
Telegram ranks this channel #27 of 85 here — alongside 84 others — read 18 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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.
“makasse's crew” (@makassescrew), 1,703 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/makassescrew.
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.