Other / unclassifiable — 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 72% 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 1 other registered channel. 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 (5 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. 3 of the 3 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 188 comparable posts for this entry, running 5 August 2026 to 28 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_mutual, 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
26 measurements spanning 96 days, net -4,220. 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,772–9,192 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
9 Nov 2026, 23:45
3,513
-24
6 Nov 2026, 22:07
3,537
-21
3 Nov 2026, 21:46
3,558
-36
31 Oct 2026, 19:18
3,594
-62
29 Oct 2026, 05:08
3,656
-171
26 Oct 2026, 06:07
3,827
-47
22 Oct 2026, 20:40
3,874
-50
19 Oct 2026, 10:14
3,924
-21
16 Oct 2026, 16:19
3,945
-26
13 Oct 2026, 21:21
3,971
-155
8 Oct 2026, 11:54
4,126
-73
2 Oct 2026, 02:18
4,199
-1,501
16 Sept 2026, 06:59
5,700
-325
12 Sept 2026, 19:18
6,025
-503
8 Sept 2026, 18:21
6,528
-1,040
3 Sept 2026, 13:37
7,568
-304
30 Aug 2026, 22:34
7,872
-173
28 Aug 2026, 08:46
8,045
-195
25 Aug 2026, 18:22
8,240
-211
22 Aug 2026, 08:05
8,451
first reading
Engagement
306 posts held, back to 5 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 21 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 306 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.
$DINGER is quietly printing
the chart has been a staircase of higher lows for 24 hours. no violent pumps, just steady, relentless buying. this is the hallmark of institutional-style accumulation on-chain.
the underlying narrative fits perfectly with the current cycle rotation.
7fmHqRpJLgpVsJFTvrv24CEjkz9c4o5uVX4Zdur1hz35
GMGN
Website | Twitter | Telegram
$LOOSE
a textbook reversal play. sellers exhausted themselves trying to break support and now the buyers are taking absolute control. the transition in momentum is clear on the tape.
first target is the previous local high.
2UMByb4bYyDqEMbGMjV36zTKHhXMQbPRWjiHfXoypump
Dexscreener · GMGN
early look at $ILLIԚUID
this is what early discovery looks like. social volume is practically zero but on-chain volume is surging. the ratio of buyers to sellers is indicating a heavy imbalance.
getting in before the broader market catches on.
j5djiWWv4rT7k9KHn6n3BwuQbVpHPrMjmTGkG5xpump
Chart
Website | Twitter
$ATH — the real deal
tired of the noise? look at this chart. no artificial spikes, just a solid, methodical climb. this is what a real community looks like when they believe in the asset.
it's rare to see something this stable at this stage of the launch.
2CqsLSTUdDqifDPXqBgowuwhWXVbf3Je5HmxCiospump
Chart · GMGN
$TOKEN — volume alert
the volume profile just shifted dramatically. we're seeing 4x the average hourly volume and the price is holding the upper bounds of the range. this is a pressure cooker ready to pop.
verified the liquidity is permanently locked.
0x69b3dd03cc143b71a7df7874c8cffbe031aa6aec
Chart
Showing the 12 most recent of 306 posts we hold for @Soniccall. 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
Named by 6 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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“Sonic Calls” (@Soniccall), 3,513 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Soniccall.
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.
