Telegram RegisterThe public register of Telegram
Telegram profile photo for PatternsHunter

Channel

PatternsHunter

@PatternsHunter

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

6,331subscribers

-161 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-1002020959293
TypeChannel
Username@PatternsHunter
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/PatternsHunter

Growth

6,3316,4926,411.57 August 2026 — 6,492 subscribers7 August 2026 — 6,492 subscribers8 August 2026 — 6,480 subscribers11 August 2026 — 6,459 subscribers15 August 2026 — 6,422 subscribers18 August 2026 — 6,397 subscribers21 August 2026 — 6,386 subscribers24 August 2026 — 6,365 subscribers27 August 2026 — 6,351 subscribers30 August 2026 — 6,331 subscribers7 August 202630 August 2026
10 measurements spanning 23 days, net -161. 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 6,307–6,516 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 18:556,331-20
27 Aug 2026, 10:346,351-14
24 Aug 2026, 08:376,365-21
21 Aug 2026, 02:186,386-11
18 Aug 2026, 07:236,397-25
15 Aug 2026, 01:376,422-37
11 Aug 2026, 12:236,459-21
8 Aug 2026, 07:216,480-12
7 Aug 2026, 12:476,492no change
7 Aug 2026, 12:356,492first reading

Engagement

18 posts held, back to 1 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.12%
avg views ÷ 6,331 subscribers
Avg views / post
134
18 posts measured
Reaction rate
0.741%
reactions ÷ views · ER floor
Posts in window
18
of 18 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. It is computed over the 1 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held18 (1 August 20268 August 2026)
Views total2,418
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:07 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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1100.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 1 of the 18 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 1 August 2026 to 8 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

8 Aug 2026, 14:57 UTC112 viewsread 12 August 2026

🎯 Recent Direction — Round Closed Asset: BTC Timeframe: 5m Direction: DOWN ↓ Confidence: 77% Result: ✅ Correct This direction was generated by the Forsee AI engine in the last session. Open the scanner — the next round is already forming.

8 Aug 2026, 06:20 UTC125 viewsread 12 August 2026

🔥 6/6 Correct — AI on Streak The AI engine has hit 6 correct directions in a row on ETH this session. NY rounds are active right now. Your quota is still available — open the scanner and catch the current round.

4 Aug 2026, 19:56 UTC222 viewsread 12 August 2026
Photo

I'll hardly be trading this week – decided to take a mini vacation. Go over today's positions – they contain all my logic and profit. 🗣 Take care of yourselves and your money! 🤝

4 Aug 2026, 17:12 UTC192 viewsread 12 August 2026

🔥 3/3 Correct — AI on Streak The AI engine has hit 3 correct directions in a row on ETH this session. NY rounds are active right now. Your quota is still available — open the scanner and catch the current round.

4 Aug 2026, 10:27 UTC173 viewsread 12 August 2026
Photo

I opened another short contract using the same logic. There’s no point waiting for the final target anymore, because I’ve basically already executed my plan. I hope you understood the logic – all you had to do was overcome laziness and just press the button when the signal came. Have a great day, everyone. 🤝

4 Aug 2026, 09:56 UTC153 viewsread 12 August 2026
Photo

I immediately opened another contract using the same logic: 1.Main move is short 2.Price is below beat 3.Huge odds on the contract (payout)

4 Aug 2026, 09:50 UTC136 viewsread 12 August 2026
Photo

That's it. All the factors aligned: 1. We determined where price was heading on the chart (short). 2. We saw synchronisation in the terminal: price was below beat. 3. We took the risk and grabbed the contract with huge odds.

4 Aug 2026, 09:40 UTC111 viewsread 12 August 2026
Photo

I'm taking this contract because of the huge odds + price is below beat.

4 Aug 2026, 09:31 UTC99 viewsread 12 August 2026
Photo

Right now is the worst condition for opening short positions, because the price is above BEAT. I’ll most likely get a second losing contract and will wait for a better opportunity.

4 Aug 2026, 09:25 UTC103 viewsread 12 August 2026
Photo

First contract missed. Let me explain the logic: Once I’ve already identified on the chart that price is moving in my direction, I want to see price trading below the beat in the terminal itself – this is essentially the spread, which gives better mathematical expectancy for the contract’s execution. Also, don’t forget about the odds on the contract – the only exception is the abuse (exploit), where the move is so ob

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

“PatternsHunter” (@PatternsHunter), 6,331 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/PatternsHunter.

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.