Channel
@faizanharoontelegram
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
48,907subscribers
-6,219 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002230950038 |
|---|---|
| Type | Channel |
| Username | @faizanharoontelegram |
| Description | Welcome to Faizan Haroon – Telegram Community To join the Private Group, message “Hi” on Instagram: @faizan._.haroon https://www.instagram.com/faizan._.haroon |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/faizanharoontelegram |
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 9 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 13:47 | 48,907 | -63 |
| 5 Nov 2026, 11:15 | 48,970 | -59 |
| 4 Nov 2026, 07:31 | 49,029 | -57 |
| 3 Nov 2026, 09:35 | 49,086 | -63 |
| 2 Nov 2026, 10:24 | 49,149 | -43 |
| 1 Nov 2026, 11:26 | 49,192 | -67 |
| 31 Oct 2026, 11:05 | 49,259 | -125 |
| 30 Oct 2026, 08:51 | 49,384 | -63 |
| 29 Oct 2026, 08:58 | 49,447 | -65 |
| 28 Oct 2026, 09:31 | 49,512 | -83 |
| 27 Oct 2026, 07:08 | 49,595 | -72 |
| 26 Oct 2026, 07:29 | 49,667 | -40 |
| 25 Oct 2026, 06:07 | 49,707 | -50 |
| 24 Oct 2026, 08:27 | 49,757 | -54 |
| 23 Oct 2026, 07:09 | 49,811 | -60 |
| 22 Oct 2026, 06:37 | 49,871 | -116 |
| 20 Oct 2026, 22:06 | 49,987 | -48 |
| 19 Oct 2026, 23:39 | 50,035 | -85 |
| 18 Oct 2026, 20:19 | 50,120 | -78 |
| 17 Oct 2026, 19:06 | 50,198 | first reading |
125 posts held, back to 29 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 186 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 125 (29 July 2026 – 7 November 2026) |
| Views total | 40,508 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Nov 2026, 12:29 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.
Lifetime counters from Telegram’s own channel header, read 7 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
Telegram’s own ‘edited’ marker: 3 of 37 posts held from the last 30 days (8.11%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Market structure: Bullish Support zone: $75,950 – $75,850 Resistance zone: $76,200 – $76,300 Reaction expectation: Price is trading near the upper edge of the channel if it breaks above resistance, upside may continue; a rejection here could send it back toward the trendline support.
Market structure: Ranging Support zone: $75,400 – $75,200 Resistance zone: $76,200 – $76,400 Reaction expectation: Price is pulling back to the middle of the range if it holds above the $75,950 area, it may bounce back toward resistance; a break below could send it toward support.
Don't count the days, make the days count. Small steps daily build empires over time.
Market structure: Ranging Support zone: $80,350 – $80,250 Resistance zone: $80,850 – $80,950 Reaction expectation: Price is testing the bottom of the range if it holds support here, a bounce back toward resistance is likely; a break below could lead to further downside.
Big profits are great, but losing everything is worse. Save your money first, profit comes later.
Market structure: Bullish Support zone: $78,000 – $77,800 Resistance zone: $78,800 – $79,000 Reaction expectation: Price is testing the lower boundary of the channel if it holds above $78,000, a bounce toward resistance is likely; a break below could lead to a deeper pullback.
BTC current direction: Ranging Nearest liquidity zone: Below price Which side likely to get liquidated first: Longs Probability of stop hunt direction: Downward
Reaction expectation: Price is moving up to test the downward trendline and resistance if it gets rejected here, a drop back to support is likely; a clean break above could shift momentum upward.
Market structure: Bearish Support zone: $77,700 – $77,600 Resistance zone: $78,200 – $78,400
Perfection is not a daily requirement. Progress is however small, however steady.
FREE SPOT SCALPING SIGNAL: LONG: INJ/USDT 📈🟢 Buying range / Entry / Dca: 7.906 - 7.000 1st (TP) take profit: 7.26 🎯 2nd (TP) take profit: 7.5 🎯 3rd (TP) take profit: 7.676 🎯 Stop loss: 6.735
FREE SPOT SCALPING SIGNAL: LONG: APT/USDT 📈🟢 Buying range / Entry / Dca: 0.635 - 0.624 1st (TP) take profit: 0.65 🎯 2nd (TP) take profit: 0.67 🎯 3rd (TP) take profit: 0.687 🎯 Stop loss: 0.605
Showing the 12 most recent of 125 posts we hold for @faizanharoontelegram. 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.
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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 24 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 20 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Faizan Haroon” (@faizanharoontelegram), 48,907 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/faizanharoontelegram.
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.