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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 4 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. 21 of the 21 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 41 comparable posts for this entry, running 6 August 2026 to 19 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).
Recorded under the key clone_copy, last confirmed 11 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
27 measurements spanning 93 days, net -1,737. 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 5,032–7,291 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
8 Nov 2026, 09:00
5,293
-30
4 Nov 2026, 20:47
5,323
-21
2 Nov 2026, 00:19
5,344
-35
29 Oct 2026, 13:59
5,379
-20
26 Oct 2026, 14:20
5,399
-20
23 Oct 2026, 22:10
5,419
-23
21 Oct 2026, 06:00
5,442
-21
18 Oct 2026, 05:26
5,463
-26
15 Oct 2026, 06:21
5,489
-24
12 Oct 2026, 02:38
5,513
-104
5 Oct 2026, 20:41
5,617
-88
28 Sept 2026, 17:00
5,705
-158
18 Sept 2026, 23:00
5,863
-60
14 Sept 2026, 11:18
5,923
-49
10 Sept 2026, 17:40
5,972
-86
5 Sept 2026, 11:21
6,058
-42
1 Sept 2026, 14:25
6,100
-59
29 Aug 2026, 17:46
6,159
-27
27 Aug 2026, 02:12
6,186
-65
23 Aug 2026, 23:18
6,251
first reading
Engagement
100 posts held, back to 6 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 13 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 100 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
5s
Average length
5s
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.
Remember #01 ? I have shared at 75k, and gone to 25-30 mil lately. I think I found a similar one on RH now.
Grabbing a bag here at $YUP - 171k
https://dexscreener.com/robinhood/0xef602666ce95a44b8e903f95b3f715fee5a055a57302f4d3f3aaa4aa4074d48e
0x2f70500f9057660B52E5A9858e1a8075c60a12fD
I also bought it via BID too, hearing good things about the team. Let's give it a try, I'll maximize my bags If It reaches to 500…
💚 MULTIPLIER DETECTED: 4x+
@ramscalls made 4x+ on DELTA.
$917K ⮕ $3.68M
🔎 Call❕💍 KOL
🆖 Set custom filters and let gems come to you through our Alerts Bot 💎
I’m calling today’s token a "banger," though you should, of course, always do your own research. When I label something a banger, it means I’m getting in and calling it at the absolute earliest stage; I call it that because—based on the team and the narrative—I believe it has the potential for massive gains (tens of Xs). As I said, do your own research, too; sometimes we can be wrong.
The launch time isn't set yet; …
Bought $PANTS on Ansem launchpad - dogwifpants
meme from 2016 and apparently where the ‘ wif ‘ meme originally came from
seems like the best wif type runner for Ansem to support on his own launchpad
Ansem sent dogwifhat to 5B
200k Dyor
FtateF34Xzawa91bpbVNdX72hZYo9cymRDYqBreHHbJi
https://dexscreener.com/solana/6tMVLioTrzW65RWRAftNWPSf1JikYWRVsP87w9h9em2a
https://t.me/thedogwifpants
🪯 DIP MODE: 2x+🔫
@ramscalls made 2x+ on PLUMBER from dip.
$623K DIP ⮕ $1.34M
🔎 Call❕💍 KOL
🆖 Set custom filters and let gems come to you through our Alerts Bot 💎
Showing the 12 most recent of 100 posts we hold for @ramscalls. 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.
Posts recorded as deleted after publishing
We recorded 3 posts on @ramscalls as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
8 August 2026
Most recent seen missing
8 August 2026
Median time before seen missing
12 hours
Seen missing in the last 30 days
0
Forward network
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 3 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.
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 8 November 2026 — this
entry's latest reading, not the date you are reading this.
“Ram’s Gems Calls ✨” (@ramscalls), 5,293 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/ramscalls.
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.