Telegram RegisterThe public register of Telegram
Telegram profile photo for Matty Pips

Channel

Matty Pips

@mattypips

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

11,053subscribers

-464 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001116590424
TypeChannel
Username@mattypips
CreatedBetween 1 February 2017 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 October 2026
Measurements held42
Confirmed unchanged1 time, most recently 17 October 2026
On Telegramt.me/mattypips

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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 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 (3 of the pairs behind the counts below)
Posted firstThenOverlapGap
@tradewithmatty/21307 Jul 2026, 21:10 UTC@mattypips/6208 · this entry7 Jul 2026, 21:10 UTC1.00under a minute
@tradewithmatty/21349 Jul 2026, 05:51 UTC@mattypips/6212 · this entry9 Jul 2026, 05:51 UTC1.00under a minute
@tradewithmatty/213921 Jul 2026, 04:39 UTC@mattypips/6219 · this entry21 Jul 2026, 04:39 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@tradewithmatty11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–2)

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 2 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 12 comparable posts for this entry, running 7 July 2026 to 4 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).

Across the whole group of 2, the earliest publisher we hold is @mattypips — 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 8 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 1 other registered channel, 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

11,05311,51711,2856 August 2026 — 11,517 subscribers6 August 2026 — 11,517 subscribers7 August 2026 — 11,512 subscribers8 August 2026 — 11,501 subscribers9 August 2026 — 11,498 subscribers10 August 2026 — 11,487 subscribers11 August 2026 — 11,470 subscribers12 August 2026 — 11,464 subscribers13 August 2026 — 11,459 subscribers15 August 2026 — 11,447 subscribers16 August 2026 — 11,434 subscribers17 August 2026 — 11,426 subscribers18 August 2026 — 11,419 subscribers19 August 2026 — 11,411 subscribers20 August 2026 — 11,401 subscribers22 August 2026 — 11,393 subscribers24 August 2026 — 11,379 subscribers25 August 2026 — 11,371 subscribers26 August 2026 — 11,367 subscribers27 August 2026 — 11,362 subscribers28 August 2026 — 11,356 subscribers29 August 2026 — 11,349 subscribers30 August 2026 — 11,342 subscribers30 August 2026 — 11,336 subscribers1 September 2026 — 11,328 subscribers2 September 2026 — 11,322 subscribers3 September 2026 — 11,313 subscribers5 September 2026 — 11,304 subscribers8 September 2026 — 11,275 subscribers11 September 2026 — 11,251 subscribers13 September 2026 — 11,238 subscribers14 September 2026 — 11,227 subscribers16 September 2026 — 11,215 subscribers18 September 2026 — 11,207 subscribers25 September 2026 — 11,178 subscribers4 October 2026 — 11,121 subscribers8 October 2026 — 11,100 subscribers13 October 2026 — 11,083 subscribers14 October 2026 — 11,073 subscribers15 October 2026 — 11,068 subscribers16 October 2026 — 11,057 subscribers17 October 2026 — 11,053 subscribers6 August 202617 October 2026
42 measurements spanning 72 days, net -464. 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 10,983–11,587 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
17 Oct 2026, 13:5011,053-4
16 Oct 2026, 15:2811,057-11
15 Oct 2026, 11:5511,068-5
14 Oct 2026, 12:2711,073-10
13 Oct 2026, 00:4911,083-17
8 Oct 2026, 18:1811,100-21
4 Oct 2026, 06:0011,121-57
25 Sept 2026, 10:1511,178-29
18 Sept 2026, 23:5811,207-8
16 Sept 2026, 15:5711,215-12
14 Sept 2026, 16:3811,227-11
13 Sept 2026, 03:1611,238-13
11 Sept 2026, 04:2011,251-24
8 Sept 2026, 03:1911,275-29
5 Sept 2026, 00:2111,304-9
3 Sept 2026, 06:3411,313-9
2 Sept 2026, 00:4411,322-6
1 Sept 2026, 00:4811,328-8
30 Aug 2026, 22:3711,336-6
30 Aug 2026, 00:2811,342first reading

Engagement

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

What this channel posts

Video runtime
1m 56s
Average length
58s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

31 Aug 2026, 05:29 UTC460 viewsread 3 September 2026
Photo

CAUGHT sooooo many pips with my live sessions and also FLOW!!! Let’s lock in and work together!! Reach out on IG @matthewthayer

24 Aug 2026, 04:56 UTC884 viewsread 3 September 2026
Photo

Setup an account at Genesis and run it up with me! 1000-30k challenge by Christmas! https://dashboard.genesisfxmarkets.com/auth/register?ref=GFX91CC2333 Send me a DM on IG and I’ll get you access to weare1mission.com to use flow!

20 Aug 2026, 01:54 UTC772 viewsread 3 September 2026
Photo

GOING LIVE!! https://app.coneqtx.com/live-sessions/detail/243/

18 Aug 2026, 23:54 UTC802 viewsread 3 September 2026
Photo

👻 MFX GHOST — NOW +20.6% 📈 We’re just getting started. If you want to follow MFX GHOST and have the trades copied automatically, get your account set up below 👇 🔗 https://dashboard.genesisfxmarkets.com/auth/register?ref=GFX91CC2333 Create account → Fund → Find MFX GHOST → Follow. Minimum to start: $300 Let’s keep running it up. 👻📈 Trading involves risk. Past performance doesn’t guarantee future results.

17 Aug 2026, 17:51 UTC754 viewsread 3 September 2026
Photo

👻 MFX GHOST IS LIVE Want to follow the same trades automatically? Get connected → fund your account → follow MFX GHOST. Minimum: $300 👇 CREATE YOUR ACCOUNT HERE https://dashboard.genesisfxmarkets.com/auth/register?ref=GFX91CC2333 Once you’re in, search MFX GHOST and start following. 📈 Trading involves risk. Results aren’t guaranteed.

12 Aug 2026, 21:40 UTC849 viewsread 3 September 2026

UP OVER 4% already! https://dashboard.genesisfxmarkets.com/copy-trading/16813475-7c9b-494c-bafa-04f34cb9606c

11 Aug 2026, 20:37 UTC719 viewsread 3 September 2026
Photo

🚨 GET PAID SESSION TONIGHT! 🚨 We’re going LIVE at 10PM EST tonight! 💰📈 Charts up. Energy high. We’re hunting setups and looking to GET PAID together LIVE. 👻🔥 If you’ve been waiting to see how we attack the markets in real time — THIS IS THE CALL. ⏰ 10PM EST TONIGHT 📍 LIVE ON ZOOM 🔥 Pull up early. 🔥 Have your charts ready. 🔥 Bring the ENERGY. MFX SQUAAD — IT’S TIME TO WORK. 🥶📈💰 👇 JOIN THE LIVE SESSION https://u…

11 Aug 2026, 05:48 UTCviews —

Matty Pips pinned «NEW MFX GHOST ON https://dashboard.genesisfxmarkets.com/copy-trading/16813475-7c9b-494c-bafa-04f34cb9606c»

Showing the 12 most recent of 33 posts we hold for @mattypips. 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 17 October 2026 — this entry's latest reading, not the date you are reading this.

“Matty Pips” (@mattypips), 11,053 subscribers as measured 17 October 2026. Telegram Register, tgregister.com/channel/mattypips.

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.