Telegram RegisterThe public register of Telegram
Telegram profile photo for Futures Spreads 3%

Channel

Futures Spreads 3%

@futures_spreads_spam

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

3,755subscribers

+49 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002776949907
TypeChannel
Username@futures_spreads_spam
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/futures_spreads_spam

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 14 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 why it has no browse page of its own yet.

Growth

3,7063,7623,7347 August 2026 — 3,706 subscribers8 August 2026 — 3,707 subscribers11 August 2026 — 3,718 subscribers14 August 2026 — 3,719 subscribers18 August 2026 — 3,720 subscribers21 August 2026 — 3,714 subscribers24 August 2026 — 3,716 subscribers27 August 2026 — 3,714 subscribers30 August 2026 — 3,710 subscribers3 September 2026 — 3,723 subscribers8 September 2026 — 3,761 subscribers12 September 2026 — 3,762 subscribers16 September 2026 — 3,755 subscribers3,7557 August 202616 September 2026
13 measurements spanning 40 days, net +49. 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 3,698–3,770 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 16:593,755-7
12 Sept 2026, 13:393,762+1
8 Sept 2026, 07:213,761+38
3 Sept 2026, 00:153,723+13
30 Aug 2026, 23:383,710-4
27 Aug 2026, 19:133,714-2
24 Aug 2026, 17:573,716+2
21 Aug 2026, 01:123,714-6
18 Aug 2026, 01:023,720+1
14 Aug 2026, 21:273,719+1
11 Aug 2026, 08:443,718+11
8 Aug 2026, 07:293,707+1
7 Aug 2026, 10:463,706first reading

Engagement

60 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 60 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 22:48 UTC12 viewsread 7 August 2026

❌ #ACE BYBIT-ASTER spread is not relevant (delisting, low liquidity, or other issues) [600.9036483764648]

7 Aug 2026, 21:52 UTC25 viewsread 7 August 2026

#GWEI aligned in 00:28 🟠Price OURBIT: $0.03221 ⚫️Price BYBIT: $0.03226

7 Aug 2026, 21:51 UTC24 viewsread 7 August 2026

📈📈#GWEI | Spread: 4.76% 📌 GWEI_USDT (COPY: GWEI) 🟢Long OURBIT : $0.031280000 🔴Short BYBIT : $0.032770000 🌗Funding OURBIT : 0.01% 🌓Funding BYBIT : -0.03% 🔍 Additional Info: ⚖️OURBIT Max Size : $262 ⏱️F/Interval BYBIT : 4H | 00:00 UTC ⏱️F/Interval OURBIT : 4H | 00:00 UTC 📝 All Exchanges Overview: ⚫️BYBIT : $0.03226 🟠OURBIT : $0.03237 🟣BINGX : $0.03239 🔵GATE : $0.032648 🟤BITGET : $

7 Aug 2026, 21:25 UTC32 viewsread 7 August 2026

#ZEST aligned in 00:21 ⚪️Price MEXC : $0.21068 🟤Price BITGET: $0.21068

7 Aug 2026, 21:25 UTC32 viewsread 7 August 2026

📈📈#ZEST | Spread: 3.80% 📌 ZEST_USDT (COPY: ZEST) 🔴Short MEXC : $0.218830000 🟢Long BITGET : $0.210810000 🌗Funding MEXC : 0.04% 🌓Funding BITGET : 0.01% 🔍 Additional Info: ⚖️MEXC Max Size : $6565 ⏱️F/Interval MEXC : 4H | 00:00 UTC ⏱️F/Interval BITGET : 4H | 00:00 UTC 📝 All Exchanges Overview: 🔵GATE : $0.20772 ⚪️MEXC : $0.20856 🟠OURBIT : $0.21048 ⚫️BYBIT : $0.2112 🟤BITGET : $

7 Aug 2026, 20:41 UTC36 viewsread 7 August 2026

#ACE aligned in 788:14 ⚫️Price BYBIT : $0.111 🟤Price BITGET: $0.1105

7 Aug 2026, 19:37 UTC50 viewsread 7 August 2026

#HFT aligned in 06:00 🔵Price GATE: $0.01345 ⚪️Price MEXC: $0.01347

7 Aug 2026, 19:35 UTC47 viewsread 7 August 2026

#POWER aligned in 00:24 ⚪️Price MEXC : $0.09389 ⚫️Price BYBIT: $0.09367

7 Aug 2026, 19:35 UTC42 viewsread 7 August 2026

📈📈#POWER | Spread: 4.19% 📌 POWER_USDT (COPY: POWER) 🟢Long MEXC : $0.090190000 🔴Short BYBIT : $0.093970000 🌗Funding MEXC : 0.01% 🌓Funding BYBIT : 0.01% 🔍 Additional Info: ⚖️MEXC Max Size : $7215 ⏱️F/Interval MEXC : 4H | 20:00 UTC ⏱️F/Interval BYBIT : 4H | 20:00 UTC 📝 All Exchanges Overview: 🔵GATE : $0.09403 ⚪️MEXC : $0.09413 ⚫️BYBIT : $0.09414 🟤BITGET : $0.09418 🟠OURBIT : $

7 Aug 2026, 19:31 UTC37 viewsread 7 August 2026

🎰🎰#HFT | Spread: 3.33% 📌 HFT_USDT (COPY: HFT) 🟢Long GATE : $0.013220000 🔴Short MEXC : $0.013660000 🌗Funding GATE : -0.17% 🌓Funding MEXC : -0.14%

7 Aug 2026, 19:21 UTC34 viewsread 7 August 2026

#MSTU aligned in 44:39 ⚪️Price MEXC : $1.9864 🟤Price BITGET: $1.9768

7 Aug 2026, 18:52 UTC32 viewsread 7 August 2026

#ACE aligned in 100:18 ⚫️Price BYBIT : $0.11595 🟢Price HLIQUID: $0.1157

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

Mentions

Named by 4 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.

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

“Futures Spreads 3%” (@futures_spreads_spam), 3,755 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/futures_spreads_spam.

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.