It was a sideways day for us, the premiums just got eroded and nothing else. Do not carry, though i am expecting an All time high this week or may be we can open gap up tomorrow, but do not carry. Don't risk your capital

Channel
StocHub - Stocks | Nifty | Banknifty | Sensex | Trading | Intraday | Swing
@StocHub
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
766subscribers
-17 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001268396918 |
|---|---|
| Type | Channel |
| Username | @StocHub |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/StocHub |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 04:10 | 766 | -3 |
| 17 Oct 2026, 06:28 | 769 | -2 |
| 10 Oct 2026, 03:15 | 771 | -6 |
| 29 Sept 2026, 13:20 | 777 | -6 |
| 13 Sept 2026, 21:22 | 783 | no change |
| 13 Sept 2026, 20:47 | 783 | first reading |
Engagement
20 posts held, back to 15 December 2025 — 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 22 December 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
Groww now at 170
Nifty 26150 ce dec end:- 154 Sl:- 130 Target:- 195-208
The way nifty is holding onto higher levels, FII's turning buyers again and those mighty gapups, it seems Nifty is all set for All time high. If you get a dip, it's a buy on dip as long as we are above 25900 levels. Market looks steady here
Nifty 26000 pe December end:- 149 Sl:- 129 Target:- 185-197
If Nifty breaks 25880 on the downside, we may turn negative again. Also banknifty has turned negative. I am not sharing any trade because we keep sl of just 20 points, but due to volatility it gets triggered. Better to let you guys know the direction of the market and the levels and you can take the trades accordingly
Even after a good gapup Nifty is struggling to move up. BANKNIFTY is only up by 80 points now, even Nifty is unable to hold higher levels. This gapup was unexpected, but it misses strength as well. We may come down in the closing. It's only Reliance that is holding Nifty up and nothing else
My stoplosses might trigger due to volatility because I can't control it, but i will be correct in predicting the direction of the Market and the levels. Warned you for not going LONG and nifty turned negative, tomorrow as well we may see good selling pressure in the index as the upper levels are unable to hold the market precisely
Sl triggered but don't go long, wait for proper levels because the Market breadth is still not good
They are trying to play with the premium of the puts. If nifty breaks 25790, it will go down again
Nifty 25900 pe 23rd December;- 118 Sl:- 97 Target:- 150+
Still not very happy with the recovery, this might be just a short covering because of oversold put call ratio. Stay cautious. Long only above 25910 levels in Nifty and Banknifty above 59290 levels
Showing the 12 most recent of 20 posts we hold for @StocHub. 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.
Appears in Telegram’s recommendations for other channels
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.
@Intradayoption_call_put · 18,870
Telegram ranks this channel #38 of 70 here — alongside 69 others — read 13 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“StocHub - Stocks | Nifty | Banknifty | Sensex | Trading | Intraday | Swing” (@StocHub), 766 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/StocHub.
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.