Telegram RegisterThe public register of Telegram
Telegram profile photo for Futures spreads 7%

Channel

Futures spreads 7%

@futuresspreds

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

821subscribers

-95 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003682902909
TypeChannel
Username@futuresspreds
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/futuresspreds

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 19 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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)
Posted firstThenOverlapGap
@futures_spreads_7/494227 Jun 2026, 16:07 UTC@futuresspreds/4502 · this entry27 Jun 2026, 16:07 UTC1.00under a minute
@futuresspreds/4504 · this entry29 Jun 2026, 04:29 UTC@futures_spreads_7/494429 Jun 2026, 04:29 UTC1.00under a minute
@futuresspreds/4505 · this entry29 Jun 2026, 11:48 UTC@futures_spreads_7/494529 Jun 2026, 11:48 UTC1.00under a minute
@futuresspreds/4509 · this entry29 Jun 2026, 13:59 UTC@futures_spreads_7/494929 Jun 2026, 13:59 UTC1.00under a minute
@futuresspreds/4511 · this entry29 Jun 2026, 17:51 UTC@futures_spreads_7/495129 Jun 2026, 17:51 UTC1.00under a minute
@futuresspreds/4515 · this entry29 Jun 2026, 22:47 UTC@futures_spreads_7/495529 Jun 2026, 22:47 UTC1.00under a minute
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
ChannelMatching postsText overlapTypical gapPublished first
@futures_spreads_711 (8/8 hand-verifiable sample passed)1.00under a minute@futures_spreads_7 (11–0)

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. None of the 11 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 27 June 2026 to 30 June 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @futures_spreads_7. That is a statement about our reading window, not a claim of authorship.

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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

821916868.57 August 2026 — 916 subscribers8 August 2026 — 916 subscribers14 August 2026 — 911 subscribers21 August 2026 — 901 subscribers27 August 2026 — 894 subscribers3 September 2026 — 890 subscribers12 September 2026 — 879 subscribers2 October 2026 — 864 subscribers13 October 2026 — 854 subscribers21 October 2026 — 845 subscribers27 October 2026 — 841 subscribers3 November 2026 — 832 subscribers10 November 2026 — 821 subscribers7 August 202610 November 2026
13 measurements spanning 95 days, net -95. 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 807–930 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 14:50821-11
3 Nov 2026, 15:29832-9
27 Oct 2026, 02:56841-4
21 Oct 2026, 00:27845-9
13 Oct 2026, 04:00854-10
2 Oct 2026, 06:38864-15
12 Sept 2026, 05:15879-11
3 Sept 2026, 22:57890-4
27 Aug 2026, 13:55894-7
21 Aug 2026, 12:03901-10
14 Aug 2026, 22:16911-5
8 Aug 2026, 01:01916no change
7 Aug 2026, 18:00916first reading

Engagement

20 posts held, back to 27 June 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 1 page 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 30 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Jun 2026, 06:09 UTC132 viewsread 8 August 2026

#VELVET aligned in 03:07 🟠Price OURBIT: $1.6101 🔴Price ASTER: $1.6146

30 Jun 2026, 06:06 UTC133 viewsread 8 August 2026

🎰🎰#VELVET | Spread: 8.63% 📌 VELVET_USDT (COPY: VELVET) 🔴Short OURBIT : $1.648600000 🟢Long ASTER : $1.517650000 🌗Funding OURBIT : 0.02% 🌓Funding ASTER : 0.00%

30 Jun 2026, 03:01 UTC133 viewsread 8 August 2026

🎰🎰#AIGENSYN | Spread: 29.56% 📌 AIGENSYN_USDT (COPY: AIGENSYN) 🟢Long MEXC : $0.028250000 🔴Short BYBIT : $0.036600000 🌗Funding MEXC : -0.03% 🌓Funding BYBIT : -0.06%

30 Jun 2026, 01:50 UTC117 viewsread 8 August 2026

#CAP aligned in 00:26 ⚫️Price BYBIT : $0.03084 🟤Price BITGET: $0.03086

30 Jun 2026, 01:49 UTC91 viewsread 8 August 2026

🎰🎰#CAP | Spread: 11.11% 📌 CAP_USDT (COPY: CAP) 🔴Short BYBIT : $0.030000000 🟢Long BITGET : $0.027000000 🌗Funding BYBIT : 0.01% 🌓Funding BITGET : 0.01%

29 Jun 2026, 22:48 UTC68 viewsread 8 August 2026

#TAC aligned in 01:09 🟤Price BITGET: $0.059047 🔴Price ASTER: $0.058815

29 Jun 2026, 22:47 UTC68 viewsread 8 August 2026

🎰🎰#TAC | Spread: 9.20% 📌 TAC_USDT (COPY: TAC) 🔴Short BITGET : $0.065518000 🟢Long ASTER : $0.060000000 🌗Funding BITGET : 0.01% 🌓Funding ASTER : 0.00% 🔍 Additional Info: ⏱️F/Interval ASTER : 1H | 23:00 UTC ⏱️F/Interval BITGET : 4H | 00:00 UTC 🟤BITGET: ⛓TON : Dep:🟢 | W/d:🟢 💼Supported networks: ⛓TON: EQBE_GBRU3MPI9HHJLJOR_KYYRHQGYCFD6EUWFA42W8T7EBP 📝 All Exchanges Overview: 🔴ASTER : $0.060007…

29 Jun 2026, 19:11 UTC55 viewsread 8 August 2026

#MANTA aligned in 01:04 ⚪️Price MEXC : $0.07376 🟤Price BITGET: $0.0741

29 Jun 2026, 19:10 UTC54 viewsread 8 August 2026

🎰🎰#MANTA | Spread: 7.37% 📌 MANTA_USDT (COPY: MANTA) 🔴Short MEXC : $0.080660000 🟢Long BITGET : $0.075120000 🌗Funding MEXC : -0.06% 🌓Funding BITGET : -0.05%

29 Jun 2026, 17:51 UTC52 viewsread 8 August 2026

#VELVET aligned in 00:23 🔵Price GATE : $1.6267 ⚫️Price BYBIT: $1.62922

29 Jun 2026, 17:51 UTC49 viewsread 8 August 2026

🎰🎰#VELVET | Spread: 8.12% 📌 VELVET_USDT (COPY: VELVET) 🟢Long GATE : $1.550180000 🔴Short BYBIT : $1.676010000 🌗Funding GATE : 0.01% 🌓Funding BYBIT : 0.05%

29 Jun 2026, 14:07 UTC52 viewsread 8 August 2026

#ANSEM aligned in 08:01 ⚪️Price MEXC : $0.0912 🔴Price ASTER: $0.0916

Showing the 12 most recent of 20 posts we hold for @futuresspreds. 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.

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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Futures spreads 7%” (@futuresspreds), 821 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/futuresspreds.

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.