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 94% 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
15 measurements spanning 51 days, net -120. 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 2,505–2,661 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
26 Sept 2026, 23:40
2,523
-21
17 Sept 2026, 15:57
2,544
-12
13 Sept 2026, 22:42
2,556
-8
10 Sept 2026, 05:20
2,564
-8
5 Sept 2026, 06:57
2,572
-4
1 Sept 2026, 06:14
2,576
-10
29 Aug 2026, 12:58
2,586
-7
26 Aug 2026, 10:11
2,593
-15
23 Aug 2026, 03:15
2,608
-8
19 Aug 2026, 14:52
2,616
-4
16 Aug 2026, 06:08
2,620
-10
12 Aug 2026, 18:54
2,630
-6
10 Aug 2026, 01:01
2,636
-5
7 Aug 2026, 08:52
2,641
-2
7 Aug 2026, 06:45
2,643
first reading
Engagement
20 posts held, back to 15 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 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 27 September 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
38s
Average length
38s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
421 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 32.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
138
32.8%
🔥
119
28.3%
👏
100
23.8%
👍
33
7.84%
🤝
10
2.38%
🐳
8
1.90%
🤩
6
1.43%
🎉
3
0.713%
🏆
3
0.713%
⚡
1
0.238%
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 20 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 421 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 15 July 2024 to 27 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.
Introducing SUITE - Enhance Your Trading Experience on SUI
Crypton core team will be leading $SUITE project on SUI network.
Crypton stakers will be receiving 10% of team revenue from SUITE utilities.
⚡️ Currently live:
- Best BuyBot on SUI that supports all DEXes and MovePump - @SuiBuyTechBot
- Fastest Trading Bot on SUI that supports all DEXes and MovePump - @SuiSniperBot
Links:
Tg - @PortalSuite
Twitter - https…
💵 Crypton stakers will get a share of SunTools Revenue
5% of SunTools team revenue will be converted to TON and shared with Crypton stakers.
📌 The day for $TOOLS first revenue share is set - October 10th
If you are willing to earn a larger share of $TOOLS revenue, you can become their holder. Here is how much a wallet from each tier would get on average, based on current revenue numbers (final amounts will be high…
⚡️ Seventh revenue share with $CRYPTON stakers & referrals is completed
Revenue shared today - 2'090 TON (over $11'500)
Total revenue shared - 90'046 TON
Total amount earned from Crypton products - 143'710 TON
Tweet - https://x.com/thetonhub/status/1836400959620026403
Introducing SunTools Tron Trade Bot - best trading bot for Tron
Built by SunTools and Crypton teams, it is a great tool to make your trading easy and comfortable on Tron.
Features include:
1️⃣ Trade with up to 40 wallets simultaneously
2️⃣ Earn 35% referral revenue from 5-layered referral system
3️⃣ Set limit orders (TP/SL)
4️⃣ Automatically perform DCA
5️⃣ Copy trades from up to 40 wallets
6️⃣ Automatically copy b…
Partnership Announcement: SunTools 🤝 Crypton
We as Crypton team have been providing strategic consulting and development assistance to SunTools since the start of their project.
By its design, $TOOLS on Tron offers a rich set of top-tier utilities similar to ours on TON.
Today they are releasing a trading/sniper bot for Tron - a product of joint work of Crypton and SunTools teams.
We are very satisfied with SunTo…
Revenue was distributed to @CryptonSuperBot referrals. Last monthly revenue share is completed. Prepare to getting it biweekly now.
Next week we will add an ability to claim referral revenue directly in the bot and get TON airdropped to your wallet anytime.
Tweet: https://x.com/thetonhub/status/1827888688925114387
⚡️ Sixth revenue share with $CRYPTON stakers is completed
Revenue shared today - 9'860 TON (over $67'000)
Total revenue shared - 87'956 TON
Total amount earned from Crypton products - 140'280 TON
Tweet - https://x.com/thetonhub/status/1827112482357276841
Note: @CryptonSuperBot referrers will receive their share by the end of this week.
🟢 Upcoming Revenue Share 🟢
Our sixth revenue share event is just around the corner, and we would like to give you some important information about how it will be performed. So far we have collected over 16’000 TON in revenue from our products since July 16th.
📌 Sixth Revshare Date: August 22nd
❗️ HOLDING $CRYPTON IS NO LONGER ENOUGH TO GET REVSHARE. YOU MUST STAKE TO RECEIVE REWARDS IN TON
Prior to sharing, all…
Crypton Revshare Leaderboard has been released
All staking data is now fully transparent and accessible to anyone.
Now you can check details of each individual wallet/stake and, as you all wanted, estimated current revenue in TON
Explore at https://staking.crypton.tools
Tweet: https://x.com/thetonhub/status/1826427538186666338
🟢 Staking contract has been verified 🟢
Now you can check for yourself that the contract is 100% safe before sending your $CRYPTON to it
Make sure that you are interacting with the official contract address:
EQBHnv8Bjm3mw06L0oeJOXy5LXt8hR-xVV5uqYe__Ti3_QcI (it might show in another form during transaction confirmation - UQBHnv8Bjm3mw06L0oeJOXy5LXt8hR-xVV5uqYe__Ti3_VrN)
Reminder:
$CRYPTON Staking is live at stakin…
🟢 Crypton Staking V1 is live 🟢
https://staking.crypton.tools (as always, try staking a smaller amount first to make sure you're doing everything right)
1. Staking: You can stake your $CRYPTON for 1, 3 or 6 months. The maximum number of stakes per wallet is 10. The minimum amount of tokens that can be staked is 0.01% of the total supply (100 $CRYPTON)
2. Unstaking: If you want to cancel the staking of your tokens…
🟢 Crypton Staking Test App is now live 🟢
❗️ DO NOT SEND YOUR REAL $CRYPTON TO STAKING TEST CONTRACT - YOU WILL LOSE IT FOREVER ❗️
https://staking.crypton.tools
You can try using the app and staking your test jettons. DM me (@CryptonLeadDev) to get them airdropped to your wallet (do not interact with random tokens that are airdropped to you - please double-check CA).
For testing purposes, durations are in days ins…
❤8👏7🔥4👍1
Showing the 12 most recent of 20 posts we hold for @cryptonportal. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 4 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.
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
2
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
2
vacant every time we have ever looked
@cryptonportal named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@suntoolstron named in 1 post, 8 August 2026 – 8 August 2026
@tonarmypl named in 1 post, 8 August 2026 – 8 August 2026
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Crypton Announcements” (@cryptonportal), 2,523 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/cryptonportal.
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.