Telegram RegisterThe public register of Telegram
Telegram profile photo for Futures Flow PRO

Channel

Futures Flow PRO

@FuturesFlowPro

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

28,788subscribers

-4,920 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001269606602
TypeChannel
Username@FuturesFlowPro
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/FuturesFlowPro

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 9 September 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 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
@Binance_PROs/3374930 Aug 2026, 03:44 UTC@FuturesFlowPro/920 · this entry30 Aug 2026, 03:44 UTC1.00under a minute
@Binance_PROs/338612 Sept 2026, 06:04 UTC@FuturesFlowPro/921 · this entry2 Sept 2026, 06:06 UTC1.002 minutes
@FuturesFlowPro/930 · this entry21 Sept 2026, 03:31 UTC@Binance_PROs/3440821 Sept 2026, 03:32 UTC1.00under a minute
@FuturesFlowPro/931 · this entry23 Sept 2026, 03:10 UTC@Binance_PROs/3447123 Sept 2026, 03:10 UTC1.00under a minute
@Binance_PROs/3451324 Sept 2026, 04:54 UTC@FuturesFlowPro/932 · this entry24 Sept 2026, 04:54 UTC1.00under a minute
@Binance_PROs/347482 Oct 2026, 03:01 UTC@FuturesFlowPro/935 · this entry2 Oct 2026, 03:01 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
@Binance_PROs15 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (14–1)

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. 1 of the 1 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 50 comparable posts for this entry, running 11 July 2026 to 12 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).

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

Recorded under the key clone_source, last confirmed 13 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

28,78833,70831,2487 August 202614 November 2026
66 measurements spanning 99 days, net -4,920. 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 28,050–34,446 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
14 Nov 2026, 16:5028,788-156
11 Nov 2026, 18:0728,944-61
9 Nov 2026, 21:4029,005-107
8 Nov 2026, 11:2129,112-79
7 Nov 2026, 03:0629,191-60
6 Nov 2026, 03:1929,251-31
5 Nov 2026, 04:3629,282-45
4 Nov 2026, 07:3729,327-110
3 Nov 2026, 09:0629,437-98
2 Nov 2026, 12:4029,535-51
1 Nov 2026, 14:2629,586-57
31 Oct 2026, 14:3729,643-48
30 Oct 2026, 17:0629,691-47
29 Oct 2026, 17:2729,738-46
28 Oct 2026, 20:3929,784-49
27 Oct 2026, 19:1129,833-41
26 Oct 2026, 20:0029,874-37
25 Oct 2026, 19:0729,911-32
24 Oct 2026, 16:0029,943-41
23 Oct 2026, 12:5829,984first reading

Engagement

51 posts held, back to 11 July 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 179 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.3%
avg views ÷ 28,788 subscribers
Avg views / post
6,430
9 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
9
of 51 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held51 (11 July 2026 – 12 November 2026)
Views total57,890
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 00:35 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
16
Links
12

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. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 9 posts held from the last 30 days (0%) 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).

12 Nov 2026, 05:43 UTC≈6,440 viewsread 17 November 2026

#TBTUSDT On Binance ( Futures ) ‼️ 📈LONG: 38.8 Leverage : 10x Target : 39.6 - 40.8 - 42.3 Stoploss : My Instruction 🥇

5 Nov 2026, 05:18 UTC≈6,450 viewsread 17 November 2026

#APPUSDT On Binance ( Futures ) ‼️ 📈LONG: 326 Leverage : 10x Target : 332 - 342 - 355 Stoploss : My Instruction 🥇

5 Nov 2026, 03:59 UTC≈6,430 viewsread 17 November 2026

#APPUSDT On Binance ( Futures ) ‼️ 📉SHORT: 322 Leverage : 10x Target : 315 - 309 - 296 Stoploss : My Instruction 🥇

2 Nov 2026, 03:10 UTC≈6,450 viewsread 17 November 2026

#LYNUSDT On Binance ( Futures ) ‼️ 📉SHORT: 181 Leverage : 10x Target : 180 - 178 - 174 Stoploss : My Instruction 🥇

27 Oct 2026, 05:39 UTC≈6,440 viewsread 17 November 2026

#BULLAUSDT On Binance ( Futures ) ‼️ 📉SHORT: 0.140 Leverage : 10x Target : 0.137 - 0.134 - 0.128 Stoploss : My Instruction 🥇

26 Oct 2026, 02:41 UTC≈6,420 viewsread 17 November 2026

#TAUSDT On Binance ( Futures ) ‼️ 📉SHORT: 0.0590 Leverage : 10x Target : 0.0578 - 0.0566 - 0.0542 Stoploss : My Instruction 🥇

22 Oct 2026, 04:19 UTC≈6,420 viewsread 17 November 2026

#MAGMAUSDT On Binance ( Futures ) ‼️ 📈LONG: 0.337 Leverage : 10x Target : 0.344 - 0.354 - 0.367 Stoploss : My Instruction 🥇

20 Oct 2026, 03:46 UTC≈6,420 viewsread 17 November 2026

#CTRUSDT On Binance ( Futures ) ‼️ 📉SHORT: 0.0177 Leverage : 10x Target : 0.0173 - 0.0169 - 0.0162 Stoploss : My Instruction 🥇

19 Oct 2026, 03:06 UTC≈6,420 viewsread 17 November 2026

#ARIAUSDT On Binance ( Futures ) ‼️ 📈LONG: 0.0503 Leverage : 10x Target : 0.0513 - 0.0529 - 0.0549 Stoploss : My Instruction 🥇

3 Oct 2026, 07:14 UTC≈6,440 viewsread 17 November 2026

#SANDUSDT On Binance ( Futures ) ‼️ 📈LONG: 0.0775 Leverage : 10x Target : 0.0791 - 0.0814 - 0.0845 Stoploss : My Instruction 🥇

2 Oct 2026, 03:01 UTC≈6,440 viewsread 17 November 2026

#SUPERUSDT On Binance ( Futures ) ‼️ 📈LONG: 0.236 Leverage : 10x Target : 0.240 - 0.247 - 0.257 Stoploss : My Instruction 🥇

28 Sept 2026, 05:50 UTC≈6,450 viewsread 17 November 2026

#ONEUSDT On Binance ( Futures ) ‼️ 📈LONG: 0.00273 Leverage : 10x Target : 0.00278 - 0.00286 - 0.00297 Stoploss : My Instruction 🥇

Showing the 12 most recent of 51 posts we hold for @FuturesFlowPro. 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 edited after publishing

@FuturesFlowPro edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
15 August 2026
Most recent edit
19 September 2026

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

“Futures Flow PRO” (@FuturesFlowPro), 28,788 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/FuturesFlowPro.

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.