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 9 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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 in near-verbatim form on 9 other registered channels. 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 (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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. 194 of the 194 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 2,788 comparable posts for this entry, running 7 August 2026 to 17 November 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).
Recorded under the keys clone_copy · clone_mutual, last confirmed 17 November 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.
Growth
65 measurements spanning 98 days, net +78,781. 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 114,509–261,444 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
14 Nov 2026, 03:08
212,161
-3,507
11 Nov 2026, 08:16
215,668
-10,328
9 Nov 2026, 15:56
225,996
+4,193
8 Nov 2026, 09:16
221,803
+2,515
7 Nov 2026, 07:02
219,288
-10,312
6 Nov 2026, 07:21
229,600
-9,765
5 Nov 2026, 07:59
239,365
-2,469
4 Nov 2026, 08:19
241,834
-2,656
3 Nov 2026, 10:06
244,490
+2,080
2 Nov 2026, 12:59
242,410
+19,189
1 Nov 2026, 11:58
223,221
+8,837
31 Oct 2026, 12:28
214,384
+18,585
30 Oct 2026, 10:17
195,799
+19,791
29 Oct 2026, 11:21
176,008
-1,584
28 Oct 2026, 07:01
177,592
-701
27 Oct 2026, 10:18
178,293
-829
26 Oct 2026, 11:38
179,122
-660
25 Oct 2026, 14:18
179,782
+351
24 Oct 2026, 12:45
179,431
+2,764
23 Oct 2026, 13:56
176,667
first reading
Engagement
2,788 posts held, back to 7 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 206 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.10%
avg views ÷ 212,161 subscribers
Avg views / post
2,330
725 posts measured
Reaction rate
0.803%
reactions ÷ views · ER floor
Posts in window
726
of 2,788 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 616 of 725 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 November 2026
Posts held
2,788 (7 August 2026 – 17 November 2026)
Views total
1,688,832
Reactions total
13,254
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 03:20 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈23,400
Videos
≈67
Links
≈4,550
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
1m 08s
Average length
34s
Measured directly from 2 videos 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
13,911 reactions across 752 posts, in 13 distinct kinds. The most used accounts for 14.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
2,011
14.5%
🔥
1,303
9.37%
🎉
1,300
9.35%
👏
1,227
8.82%
🏆
1,213
8.72%
🤩
1,201
8.63%
👍
1,158
8.32%
🤝
1,135
8.16%
💯
1,125
8.09%
😍
1,119
8.04%
👌
1,097
7.89%
🕊
12
0.086%
❤🔥
10
0.072%
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 753 of the 1,000 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 13,911 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 9 October 2026 to 17 November 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
Telegram’s own ‘edited’ marker: 5 of 726 posts held from the last 30 days (0.689%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#24221 - $AGT - Mcap 86.31M$ - 24h Sentiment -5.02 Bearish
SC02 M1 - pending Long order. Entry lies within HVN + not affected by any weak zone, the current support zone is approximately 1.02% wide. The uptrend has lasted 4 hours and 8 minutes, with the largest recorded price increase of 8.31%. If price breaks below this support zone, an immediate strong downward reversal is unlikely; the Short chase order can be ski…
#24220 - 🏆 Bitget CFD Championship Phase 22 Is LIVE!
Get ready to compete for a share of the $75,000 prize pool! 🚀
🗓 Event Period: Nov 16 - 23 (UTC+8)
🎁 Four Ways to Win:
✅ Mystery Blind Box: Complete CFD trading tasks to earn draw chances.
✅ Referral Bonus: Invite new CFD users and earn 3 USDT each for both inviter and invitee. Qualified referrals can also share a $4,000 prize pool, with up to $100 extra for to…
#24219 - US tightens AI chip controls and remote computing access
🏛 On November 16, BIS announced a rule to curb Chinese companies’ access to AI computing through overseas data centers.
🌐 Advanced AI chips shipped to Singapore, Malaysia, Thailand, Indonesia and Brazil will face additional licensing requirements. Certain US-linked recipients qualify for an exclusion if reporting conditions are met.
☁️ The rule also…
#24218 - $ASTER – Liquidation Map (7 days) – Index ~0.576
🧭 Favor a short-liquidation sweep at 0.580–0.582, particularly around 0.581. This cluster is closer to price than the large long cluster at 0.563–0.566, despite larger estimated cumulative long exposure.
🔺 Breaking and holding above 0.582 after the sweep would shift focus to 0.585–0.588, then 0.592–0.594. The cluster around 0.593 stands out, approaching the …
#24217 - $HUMA - Mcap 35.54M$ - 24h Sentiment +3.90 Bullish
SC02 M5 - pending Long order. Entry lies within LVN + not affected by any weak zone, the current support zone is approximately 8.56% wide. The uptrend has lasted 14 hours and 5 minutes, with the largest recorded price increase of 61.55%. If price breaks below this support zone, the trend is likely to reverse downward.
#24216 - $RARE - Mcap 11.31M$ - 24h Sentiment +2.00 Bullish
SC02 M15 - pending Long order. Entry lies within LVN + not affected by any weak zone, the current support zone is approximately 14.05% wide. The uptrend has lasted 1 day, 3 hours and 45 minutes, with the largest recorded price increase of 101.82%. If price breaks below this support zone, price is likely to reverse downward.
#24215 - 💎 Gate Launchpool $VLX Staking is Growing
Stake $BTC, $ETH, or $VLX to Share 454,546 $VLX:
⏺ Over 17,000 $ETH and 640 $BTC Staked; Est. APR Up to 112.09%
⏺ $BTC/$ETH Limits Unlock 1:1 with Net Deposits
⏺ Rewards are Distributed Hourly
🗓 11:00 AM, November 7 - 11:00 AM, November 21 (UTC)
🔥 Early Stake Now: https://www.gate.com/launchpool/VLX?pid=557
Learn More: https://www.gate.com/announcements/article/10…
#24214 - Wall Street falls sharply ahead of Nvidia earnings
📉 At the November 16 close, the Nasdaq fell 2.49%, the S&P 500 lost 1.92%, and the Dow Jones declined 1.41%. Technology stocks continued to lead the retreat.
💻 Nvidia dropped about 4.1%, while other chipmakers also faced selling pressure. Its leadership transition has heightened attention on the upcoming report.
📊 Declining stocks outnumbered advancers ro…
#24213 - $UNI – Liquidation Map (7 days) – Index ~5.16
🧭 Favor a short-liquidation sweep into 5.25–5.31 if price breaks and holds above 5.24. This is a dense upside cluster, particularly around 5.25–5.28, while 5.17–5.24 is comparatively sparse.
🔺 Holding above 5.31 after the sweep would shift focus to 5.34–5.36, followed by 5.40–5.42. A sustained move above 5.42 would bring smaller clusters at 5.45–5.48 into view.…
#24212 - ⚠️ Reminder 7 ⚠️
📊 When using VPFR with SC02, many traders only ask whether the current Entry zone is good enough to place an order. In practice, VPFR can also help determine whether a setup should keep both the primary and chase orders, or only the primary order.
🔹 If the entire Entry zone is inside an HVN and the SL also remains within a high-volume area, removing the chase order may be worth considering…
#24211 - $BLESS - Mcap 49.64M$ - 24h Sentiment +3.37 Bullish
SC02 M5 - pending Long order. Entry lies within HVN + not affected by any weak zone, the current support zone is approximately 9.08% wide. The uptrend has lasted 17 hours and 35 minutes, with the largest recorded price increase of 117.46%. If price breaks below this support zone, the trend is likely to reverse downward.
#24210 - $ZEC - Mcap 15.15B$ - 24h Sentiment Neutral
SC02 H1 - pending Short order. Entry lies within HVN + not affected by any weak zone, the current resistance zone is approximately 6.02% wide. The downtrend has lasted 8 days and 2 hours, with the largest recorded price decline of 36.92%. If price breaks above this resistance zone, price is likely to reverse upward.
👌1🤩1
Showing the 12 most recent of 2,788 posts we hold for @Scalping00x. 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.
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
@Scalping00x 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.
@hoangnh4 named in 1 post, 2 November 2026 – 2 November 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 14 November 2026 — this
entry's latest reading, not the date you are reading this.
“ScalpingX” (@Scalping00x), 212,161 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Scalping00x.
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.