Telegram RegisterThe public register of Telegram

Channel

Andrew Tate Signals

@Andrew_Tate_Signals

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Cite this entry

7,963subscribers

-59 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-1001958491162
TypeChannel
Username@Andrew_Tate_Signals
Description#Andrew #Tate #Signals
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/Andrew_Tate_Signals

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

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 word for word on 3 other registered channels. 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
@Andrew_Tate_Signals/768 · this entry14 Sept 2025, 11:54 UTC@Mexc_Signals_Pumps/67914 Sept 2025, 11:54 UTC1.00under a minute
@Andrew_Tate_Signals/769 · this entry14 Sept 2025, 12:42 UTC@Mexc_Signals_Pumps/68014 Sept 2025, 12:42 UTC1.00under a minute
@Andrew_Tate_Signals/773 · this entry16 Sept 2025, 16:22 UTC@Mexc_Signals_Pumps/68416 Sept 2025, 16:22 UTC1.00under a minute
@Andrew_Tate_Signals/776 · this entry16 Sept 2025, 20:37 UTC@Mexc_Signals_Pumps/68716 Sept 2025, 20:37 UTC1.00under a minute
@Andrew_Tate_Signals/777 · this entry16 Sept 2025, 20:46 UTC@Mexc_Signals_Pumps/68816 Sept 2025, 20:46 UTC1.00under a minute
@Andrew_Tate_Signals/780 · this entry17 Sept 2025, 19:11 UTC@Mexc_Signals_Pumps/69117 Sept 2025, 19:11 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@Mexc_Signals_Pumps9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (90)
@Memecoins_Aicoins_Crypto9 (8/8 hand-verifiable sample passed)1.00under a minute@Memecoins_Aicoins_Crypto (90)
@kucoinpump9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (90)

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 9 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 10 comparable posts for this entry, running 14 September 2025 to 18 September 2025. 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).

Across the whole group of 4, the earliest publisher we hold is @Memecoins_Aicoins_Crypto. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

7,9638,0227,992.57 August 2026 — 8,022 subscribers7 August 2026 — 8,022 subscribers7 August 2026 — 8,015 subscribers11 August 2026 — 7,963 subscribers7 August 202611 August 2026
4 measurements spanning 4 days, net -59. 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 7,954–8,031 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 01:347,963-52
7 Aug 2026, 20:218,015-7
7 Aug 2026, 12:008,022no change
7 Aug 2026, 11:528,022first reading

Engagement

20 posts held, back to 13 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 19 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
177
Videos
14
Links
123

Lifetime counters from Telegram’s own channel header, read 12 August 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

19 Sept 2025, 00:58 UTC≈2,080 viewsread 12 August 2026

Buy $MUBARAK below $0.042. First target $0.05 Buying heavily here🚀

19 Sept 2025, 00:01 UTC≈2,090 viewsread 12 August 2026
Photo

$MUBARAK (Binance Futures) Don't miss $MUBARAK Buying a heavy bag here💰

18 Sept 2025, 23:45 UTC≈2,020 viewsread 12 August 2026
Photo

LONGING $MUBARAK HERE Exchange: Binance / Binance Futures Leverage: 5-10x Breakout confirmed. Buying $MUBARAK heavily here, easy 3-5x move🐋 Targets: 0.038 - 0.040 - 0.044 - 0.048 - 0.058 - 0.062 - OPEN SL: Below 0.037

18 Sept 2025, 23:08 UTC≈1,560 viewsread 12 August 2026
Photo

🛎GEM ANNOUNCEMENT🛎 THIS IS IT🔥 In an hour, we will be sharing the biggest gem of 2025. Get ready, the show is about to start🚀

17 Sept 2025, 20:31 UTC≈1,050 viewsread 12 August 2026
Photo

$BAS (Binance Futures) Don't miss $BAS Buying a heavy bag here💰

17 Sept 2025, 20:21 UTC922 viewsread 12 August 2026
Photo

LONGING $BAS HERE Exchange: Binance Futures Leverage: 5-10x Bottom confirmed. Longing $BAS heavily here, easy 3-5x move🐋 SL: Below 0.0168

17 Sept 2025, 19:11 UTC740 viewsread 12 August 2026
Photo

🛎GEM ANNOUNCEMENT🛎 GET READY🔥🚀 In an hour, we will be sharing the biggest Binance Futures gem of 2025. Get ready, the show is about to start🚀

17 Sept 2025, 15:26 UTC629 viewsread 12 August 2026
Photo

$BULLA (Binance Futures) High Reached : $0.07844✅ Profit: 101% on just 10x lev🚀

16 Sept 2025, 20:46 UTC622 viewsread 12 August 2026
Photo

LONGING $BULLA HERE Exchange: Binance Futures Leverage: 5-10x Easiest 3-5x currently on Binance. Fully Bottomed and ready to rock. Buying $BULLA heavily here🐋 SL: Below 0.06

16 Sept 2025, 20:37 UTC518 viewsread 12 August 2026
Photo

🛎GEM ANNOUNCEMENT🛎 THIS IS IT🔥🔥 15 Minutes Left! We have found the most undervalued coin on Binance, and in 15 minutes, we’ll give it to you. This is an easy 3-5x setup, and it won’t wait for anyone Get ready, the show is about to start🚀

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

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

“Andrew Tate Signals” (@Andrew_Tate_Signals), 7,963 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Andrew_Tate_Signals.

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.