Channel
@pivotcalls
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
25,344subscribers
-353 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001142313730 |
|---|---|
| Type | Channel |
| Username | @pivotcalls |
| Created | Between 1 July 2016 and 29 February 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/pivotcalls |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 14:58 | 25,344 | -40 |
| 6 Sept 2026, 05:59 | 25,384 | -33 |
| 3 Sept 2026, 22:18 | 25,417 | -18 |
| 2 Sept 2026, 12:34 | 25,435 | -11 |
| 1 Sept 2026, 11:23 | 25,446 | -14 |
| 31 Aug 2026, 08:54 | 25,460 | -6 |
| 30 Aug 2026, 05:47 | 25,466 | -4 |
| 29 Aug 2026, 04:55 | 25,470 | -11 |
| 28 Aug 2026, 03:04 | 25,481 | -12 |
| 27 Aug 2026, 04:38 | 25,493 | -2 |
| 26 Aug 2026, 06:13 | 25,495 | -10 |
| 25 Aug 2026, 03:14 | 25,505 | -17 |
| 23 Aug 2026, 18:24 | 25,522 | -14 |
| 22 Aug 2026, 04:18 | 25,536 | -12 |
| 20 Aug 2026, 19:03 | 25,548 | -10 |
| 19 Aug 2026, 16:05 | 25,558 | -13 |
| 18 Aug 2026, 17:42 | 25,571 | -8 |
| 17 Aug 2026, 19:25 | 25,579 | -10 |
| 16 Aug 2026, 14:46 | 25,589 | -25 |
| 14 Aug 2026, 20:15 | 25,614 | first reading |
26 posts held, back to 26 June 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 58 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 3 September 2026 |
|---|---|
| Posts held | 26 (26 June 2026 – 3 September 2026) |
| Views total | 21,660 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:34 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.
That’s the power of the Virgin CPR — it acts like a magnet zone where price reacts strongly, either taking support or facing resistance. This Virgin CPR concept is explained in detail in Page No. 81 in Traders HandBook https://shop.pivotcall.com/product/handbook/
Most traders use CPR (Central Pivot Range) for daily bias —but very few understand one of its most powerful concepts: Virgin CPR. A Virgin CPR is formed when, on a particular trading day, price never enters or touches the CPR zone throughout the entire session. That untouched CPR remains “virgin” — and becomes a powerful support or resistance level for the next day. In simple words: If the price completely stays a…
If you go back and study historical charts on daily time frame, you'll notice this behavior repeatedly. Many gaps eventually get filled because gaps act like magnets, attracting price back towards them. But remember... This does not mean every gap will be filled immediately or that every gap fill will result in a reversal. Instead, treat gap areas as high-probability price action zones where the market deserves y…
One of the popular sayings in Price Action Trading is: "Markets don't like gaps." What does that mean? Whenever a gap is created on the chart, the market has a tendency to revisit that area and eventually fill the gap. While there is no guarantee about when it will happen, many gaps do get filled over time. Take Nifty as an example. Between 28th July and 29th July, a significant gap was created on daily chart. A…
That same Demand Zone (on 17th August), which previously was a support since it attracted buyers, now became a Resistance Zone because Nifty opened below it. Notice the repeated upper wicks around the zone — showing that sellers were defending the level. Then came a strong full-body bearish candle(6th candle), indicating now sellers have taken full control and then Nifty drifted down. The key lesson: Don't just d…
Supply & Demand Zones Are NOT Single Horizontal Lines. One of the common mistakes traders make is marking Supply and Demand Zones as a single horizontal line. Remember: Previous Day High (PDH) & Previous Day Low (PDL) can be marked as horizontal lines. Swing Highs & Swing Lows can also be marked as horizontal levels. But Supply & Demand are zones — not single horizontal lines. Always mark them as a zone or area,…
But once price started consolidating and then broke the 20 EMA(on 5 min chart) on the upside, it was an important indication that the selling momentum was weakening and a possible reversal was developing. And that's exactly what happened. Bank Nifty made a strong V-reversal and closed strongly on the upside. Traders who blindly shorted the opening candle, assuming it would be a downtrend day, eventually got trappe…
A Strong Breakout Does NOT Always Mean the Trend Will Continue. Yesterday, 17th August, Bank Nifty opened with a strong bearish candle and broke PDL right at the opening. Initially, everything looked like a strong downtrend day. But around 10:25 AM, the selling momentum stopped. Price started consolidating and eventually made a sharp V-reversal, moving strongly higher. So the important question is: How do you kn…
When Bank Nifty revisited the same level Yesterday, on 7th August, buyers stepped in once again, and the market bounced from that exact level. The lesson is simple: When PDH + Supply Zone or PDL + Demand Zone coincide, that level becomes a Confluence Zone—and the probability of it acting as a strong resistance or support increases significantly. This concept is explained in detail in The Trader's Handbook Page 279…
Yesterday, I explained why not every Previous Day High (PDH) and Previous Day Low (PDL) is equally important. In yesterday's post, we saw how Nifty reversed from the Previous Day High because it was not just a PDH—it was also a strong Supply Zone. Today, let's look at the opposite example in Bank Nifty. Yesterday, 7th August, Bank Nifty took support exactly at the Previous Day Low and bounced sharply. Was it simp…
Because the 5th August (Wednesday) High was not just a Previous Day High(PDH) It was also a Supply Zone. A strong bearish move had started from that level right at opening on 5th August, which tells us that aggressive sellers were already present there at PDH. When price revisited the same level yesterday, those sellers became active again, causing the reversal and breakout to fail. The same principle applies to th…
Not every Previous Day High (PDH) or Previous Day Low (PDL) is an important support or resistance level. One of the biggest mistakes traders make is assuming that every PDH and PDL will work as support or resistance. They don't. The real question is: How do you identify which PDH/PDL is powerful and which isn't? Take Nifty on 6th August (Yesterday) as an example. Price initially broke above the Previous Day High…
Showing the 12 most recent of 26 posts we hold for @pivotcalls. 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.
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 3 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Pivot Call” (@pivotcalls), 25,344 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pivotcalls.
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.