Telegram RegisterThe public register of Telegram
Telegram profile photo for Free Intraday | Positional | Multibagger Price Action Trade Calls 💹

Channel

Free Intraday | Positional | Multibagger Price Action Trade Calls 💹

@priceactionbuyer

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

343subscribers

-9 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001225276656
TypeChannel
Username@priceactionbuyer
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/priceactionbuyer

Topic

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 22 September 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.

Growth

343352347.56 August 2026 — 352 subscribers6 August 2026 — 352 subscribers19 August 2026 — 349 subscribers11 September 2026 — 348 subscribers26 September 2026 — 347 subscribers8 October 2026 — 343 subscribers6 August 20268 October 2026
6 measurements spanning 63 days, net -9. 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 342–353 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 02:02343-4
26 Sept 2026, 23:18347-1
11 Sept 2026, 07:16348-1
19 Aug 2026, 19:12349-3
6 Aug 2026, 21:17352no change
6 Aug 2026, 05:47352first reading

Engagement

20 posts held, back to 19 February 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 31 October 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

38 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 36.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1436.8%
🔥1334.2%
👍1128.9%

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 19 of the 20 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 19 February 2023 to 31 October 2025, 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

14 Jun 2025, 17:38 UTC≈3,530 views2 reactionsread 6 August 2026
File

Nifty View 16:06:25 using Pivot Point Disclaimer: This channel owner is not a SEBI registered, calls only for educational purposes only.

❤1👍1

12 Jun 2025, 17:19 UTC≈2,340 views0 reactionsread 6 August 2026
File

Nifty View 13:06:25 using Pivot Point Expecting more down fall on tomorrow .🙈 Disclaimer: This channel owner is not a SEBI registered, calls only for educational purposes only.

11 Jun 2025, 17:43 UTC≈1,420 views0 reactionsread 6 August 2026
File

Nifty View 12:06:25 using Pivot Point Premium very low & ATM IV very high, Safe trader avoid trade tomorrow, Remember Tomorrow Expiry Day . Disclaimer: This channel owner is not SEBI registered, calls only for educational purposes only.

10 Jun 2025, 17:54 UTC≈1,110 views1 reactionsread 6 August 2026
File

Nifty View 11:06:25 using Pivot Point Premium very low wait and take pull back entry using S1, S2, R1 & R2 Levels !!! Disclaimer: This channel owner is not a SEBI registered, calls only for educational purposes only.

❤1

9 Jun 2025, 16:58 UTC≈1,970 views2 reactionsread 6 August 2026
File

*Nifty View For 10:06:25* Pivot levels are very close, More chance big movement on tomorrow.👍 Disclaimer: This channel owner is not a SEBI registered, calls only for educational purposes only.

❤2

7 Jun 2025, 12:33 UTC≈2,450 views5 reactionsread 6 August 2026
File

Nifty View 09:06:25 using Pivot Point If sustain R1 above next tgt R2 If not sustain R1 to sell change R1 to S1 Tgt. Buy chance S1 to PP & R1 Tgt Sell chance S1 below S2 tgt PP to S1 and R1 range area - Range trend Disclaimer: This channel owner is not a SEBI registered, calls only for educational purposes only.

❤5

2 Feb 2025, 10:53 UTC≈2,210 views1 reactionsread 6 August 2026

💡Positional SELAN 💡 Buy 660 RS to 650 RS range. SL 564 below day close. 💰Hold next 3 to 5 Years💰

🔥1

2 Feb 2025, 10:36 UTC≈2,270 views2 reactionsread 6 August 2026

💡Positional AMBUJACEM 💡 Buy 490 RS to 505 RS range. SL 429 below day close. 💰Hold next 3 to 5 Years💰

👍1🔥1

7 Jan 2025, 17:09 UTC≈3,940 views2 reactionsread 6 August 2026

💡Positional Marksans 💡 Buy 290 RS to 285 RS range. SL 245 below day close. 💰Hold next 3 to 5 Years💰

🔥2

19 Nov 2024, 17:09 UTC≈4,010 views5 reactionsread 6 August 2026

💡Positional KNRCON 💡 Buy 290 RS to 310 RS range. SL 230 below close. 💰Hold next 3 to 5 Years💰

🔥3👍2

19 Nov 2024, 17:07 UTC≈3,490 views3 reactionsread 6 August 2026

💡Positional SAKSOFT 💡 Buy 210 RS to 216 RS range. SL 175 below day close 💰Hold next 3 to 5 Years💰

👍2🔥1

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

“Free Intraday | Positional | Multibagger Price Action Trade Calls 💹” (@priceactionbuyer), 343 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/priceactionbuyer.

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.