Telegram RegisterThe public register of Telegram
Telegram profile photo for Binance Futures/Bybit/Kucoin/Bitget/BingX Signals & Bot

Channel

Binance Futures/Bybit/Kucoin/Bitget/BingX Signals & Bot

@progrouptraders

On this record: Topic · Observations · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

4,834subscribers

-4,621 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001387191108
TypeChannel
Username@progrouptraders
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/progrouptraders

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 11 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. 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
@binancefuturesignal/371869 Aug 2026, 08:01 UTC@progrouptraders/21786 · this entry9 Aug 2026, 08:01 UTC1.00under a minute
@progrouptraders/21818 · this entry13 Aug 2026, 13:03 UTC@binancefuturesignal/3721913 Aug 2026, 13:04 UTC1.0072 seconds
@binancefuturesignal/3723114 Aug 2026, 18:53 UTC@progrouptraders/21829 · this entry14 Aug 2026, 18:54 UTC1.00under a minute
@binancefuturesignal/3723314 Aug 2026, 20:08 UTC@progrouptraders/21830 · this entry14 Aug 2026, 20:08 UTC1.00under a minute
@binancefuturesignal/3728423 Aug 2026, 10:34 UTC@progrouptraders/21872 · this entry23 Aug 2026, 10:35 UTC1.00under a minute
@binancefuturesignal/3728724 Aug 2026, 12:35 UTC@progrouptraders/21875 · this entry24 Aug 2026, 12:35 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
@binancefuturesignal8 (8/8 hand-verifiable sample passed)1.00under a minute@binancefuturesignal (7–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. 7 of the 7 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 92 comparable posts for this entry, running 3 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_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

4,8349,4557,144.56 August 2026 — 9,455 subscribers6 August 2026 — 9,455 subscribers10 August 2026 — 9,448 subscribers12 August 2026 — 9,445 subscribers16 August 2026 — 9,432 subscribers19 August 2026 — 9,424 subscribers22 August 2026 — 9,410 subscribers25 August 2026 — 9,401 subscribers28 August 2026 — 9,392 subscribers31 August 2026 — 9,383 subscribers4 September 2026 — 9,363 subscribers9 September 2026 — 9,328 subscribers13 September 2026 — 9,313 subscribers17 September 2026 — 9,293 subscribers26 September 2026 — 9,277 subscribers5 October 2026 — 9,260 subscribers11 October 2026 — 9,250 subscribers14 October 2026 — 9,246 subscribers18 October 2026 — 9,236 subscribers21 October 2026 — 9,228 subscribers24 October 2026 — 6,514 subscribers27 October 2026 — 6,513 subscribers29 October 2026 — 5,699 subscribers1 November 2026 — 5,672 subscribers4 November 2026 — 5,668 subscribers7 November 2026 — 5,006 subscribers11 November 2026 — 4,859 subscribers16 November 2026 — 4,834 subscribers6 August 202616 November 2026
28 measurements spanning 102 days, net -4,621. 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 4,141–10,148 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
16 Nov 2026, 22:384,834-25
11 Nov 2026, 12:594,859-147
7 Nov 2026, 20:565,006-662
4 Nov 2026, 12:065,668-4
1 Nov 2026, 12:085,672-27
29 Oct 2026, 16:415,699-814
27 Oct 2026, 00:316,513-1
24 Oct 2026, 03:576,514-2,714
21 Oct 2026, 08:269,228-8
18 Oct 2026, 01:379,236-10
14 Oct 2026, 20:309,246-4
11 Oct 2026, 05:419,250-10
5 Oct 2026, 07:229,260-17
26 Sept 2026, 19:159,277-16
17 Sept 2026, 17:199,293-20
13 Sept 2026, 13:009,313-15
9 Sept 2026, 22:369,328-35
4 Sept 2026, 07:179,363-20
31 Aug 2026, 19:469,383-9
28 Aug 2026, 18:479,392first reading

Engagement

126 posts held, back to 3 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 33 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 126 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏360.0%
❤120.0%
🔥120.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 126 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 126 most recent posts we hold, published 3 August 2026 to 28 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Aug 2026, 11:23 UTC30 viewsread 29 August 2026

Here you will see the Binance Futures/Bybit/OKX/Kucoin Futures Special Signals Results for (27th August 2026): 💰💰Total Profit in a day - 40% Profit ✅#EDEN-USDT - 40% profit 👇Stop Loss Trades (in %) ❌ 👁‍🗨Contact @trendalpha to enter the most profitable Futures Premium Signal Group

28 Aug 2026, 09:01 UTC33 viewsread 29 August 2026

🔥🔥 144% Profit from 50x Leverage on this #PUMP/USDT Free Signal🔥🔥 💰💰 #PUMP/USDT has hit 50310 so far to result in Huge Profit 🎯🎯 Every free signal shared here has been excellent - This is great profit on Futures Market 👁‍🗨Contact @trendalpha to enter the premium group & make daily gains on Futures as well as Spot Market

27 Aug 2026, 19:51 UTC38 viewsread 29 August 2026
Photo

🚀🚀#SOL is flying high - We continue to HODL it 👁‍🗨Contact @trendalpha to enter the premium group & trade with perfect targets & stop loss levels

27 Aug 2026, 15:58 UTC41 viewsread 29 August 2026

🎁🎁🎈Avail the Special Offer to enter the Binance Futures/Bybit/Kucoin/OKEX/Bitget/BingX Premium Group for lifetime access - Yes, we are the Futures Trend Detector 🕐🕐Offer valid for only 6 hours 🔸Pay just $55 for 3 month instead of $130 🔸Pay just $99 for lifetime access instead of $900 (Most Popular) You get all the following amazing benefits👇 ➕Daily High Quality Binance Futures/Bybit/Kucoin/OKEX/Bitget/BingX Signa…

27 Aug 2026, 15:55 UTC33 viewsread 29 August 2026
Photo

🚀🚀#HYPE/USDT FREE signal is in great profit - This shows why our accuracy is the best 👁‍🗨Contact @trendalpha to enter the premium group

27 Aug 2026, 09:37 UTC35 viewsread 29 August 2026
Photo

❇️❇️ 40% Profit on #EDEN/USDT through the Cornix Bot ✅✅It has completed all the Profit Targets on Binance Futures, Bitget Futures, ByBit USDT, KuCoin Futures, OKX Futures 📞Contact @trendalpha to enter the Binance Futures/Bybit/OKEX/Kucoin Trend Detector Premium Group

27 Aug 2026, 07:31 UTC40 viewsread 29 August 2026

🔥🔥 65% Profit from 50x Leverage on this #PUMP/USDT Free Signal🔥🔥 💰💰 #PUMP/USDT has hit 49540 so far to result in Huge Profit 🎯🎯 Every free signal shared here has been excellent - This is great profit on Futures Market 👁‍🗨Contact @trendalpha to enter the premium group & make daily gains on Futures as well as Spot Market

27 Aug 2026, 04:39 UTC42 viewsread 29 August 2026

Here you will see the Binance Futures/Bybit/OKX/Kucoin Futures Special Signals Results for (26th August 2026): 💰💰Total Profit in a day - 40% Profit ✅#BTR-USDT - 40% profit 👇Stop Loss Trades (in %) ❌ 👁‍🗨Contact @trendalpha to enter the most profitable Futures Premium Signal Group

26 Aug 2026, 11:55 UTC50 viewsread 29 August 2026

🔥 A Decent Profit on this #PUMP/USDT Free Signal! 🔥 ✅ #PUMP/USDT has hit 49240 so far resulting in good profit

26 Aug 2026, 11:06 UTC48 viewsread 29 August 2026

💥 Bitcoin appears to be in the early stages of a bull market, but confirmation will only come with a decisive breakout above the 365-day moving average at $83,000.

26 Aug 2026, 09:43 UTC49 viewsread 29 August 2026
Photo

❇️❇️ 40% Profit on #BTR/USDT through the Cornix Bot ✅✅It has completed all the Profit Targets on Binance Futures, Bitget Futures, ByBit USDT, KuCoin Futures, OKX Futures 📞Contact @trendalpha to enter the Binance Futures/Bybit/OKEX/Kucoin Trend Detector Premium Group

26 Aug 2026, 06:13 UTC47 viewsread 29 August 2026

🛎#FREESIGNAL Make a LONG/BUY on #PUMP/USDT from 48900 on Futures Leverage - 5x - 10x - 25x - 50x 👁‍🗨Contact @trendalpha to enter the premium group & trade with perfect targets & stop loss levels

Showing the 12 most recent of 126 posts we hold for @progrouptraders. 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 1 post on @progrouptraders 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
21 August 2026
Most recent seen missing
21 August 2026
Median time before seen missing
18 hours
Seen missing in the last 30 days
0

Mentions

Named by 1 registered channel — 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

DegenPump™ Crypto Pump Signals
@degenpump_crypto_pump_signals · 26,350
Telegram ranks this channel #5 of 49 here — alongside 48 others — read 8 September 2026
FAT PIG SIGNALS ™️
@btctradingprofit · 28,830
Telegram ranks this channel #9 of 49 here — alongside 48 others — read 6 September 2026
Crypto Futures Signals
@CryptoTradingWolf · 39,707
Telegram ranks this channel #20 of 57 here — alongside 56 others — read 29 August 2026
Crypto Pump Island
@crypto_pump_island · 20,087
Telegram ranks this channel #81 of 81 here — alongside 80 others — read 14 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Binance Futures/Bybit/Kucoin/Bitget/BingX Signals & Bot” (@progrouptraders), 4,834 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/progrouptraders.

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.