CALL OPTIONS - BUY MUTHHOOTFIN 3150 CE ABOVE 87 TRGT 98 110 124 SL??
Channel
STOCKS OPTIONS KING🫅🏻
@stock_cepe07
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,713subscribers
-177 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001419117763 |
|---|---|
| Type | Channel |
| Username | @stock_cepe07 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/stock_cepe07 |
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 15 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 20:49 | 2,713 | -4 |
| 11 Nov 2026, 09:21 | 2,717 | -4 |
| 7 Nov 2026, 14:09 | 2,721 | -7 |
| 4 Nov 2026, 18:00 | 2,728 | -5 |
| 1 Nov 2026, 08:55 | 2,733 | -6 |
| 29 Oct 2026, 16:39 | 2,739 | -7 |
| 26 Oct 2026, 15:59 | 2,746 | -4 |
| 23 Oct 2026, 23:40 | 2,750 | -7 |
| 21 Oct 2026, 00:48 | 2,757 | -6 |
| 17 Oct 2026, 14:58 | 2,763 | -4 |
| 14 Oct 2026, 09:50 | 2,767 | -3 |
| 11 Oct 2026, 01:58 | 2,770 | -14 |
| 5 Oct 2026, 00:36 | 2,784 | -21 |
| 25 Sept 2026, 23:42 | 2,805 | -14 |
| 17 Sept 2026, 12:00 | 2,819 | -8 |
| 13 Sept 2026, 07:58 | 2,827 | -7 |
| 9 Sept 2026, 20:35 | 2,834 | -9 |
| 4 Sept 2026, 16:00 | 2,843 | -4 |
| 1 Sept 2026, 07:38 | 2,847 | -5 |
| 29 Aug 2026, 00:47 | 2,852 | first reading |
Engagement
20 posts held, back to 8 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 2 pages 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 10 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
MPHASIS 2300 CE 90⏫⏫⏫
MPHASIS 2300 CE 89⏫⏫⏫
MPHASIS 2300 CE 88⏫⏫⏫
MPHASIS 2300 CE 87⏫⏫⏫
MPHASIS 2300 CE 86⏫⏫⏫
MPHASIS 2300 CE 85⏫⏫⏫
MPHASIS 2300 CE 84.50⏫⏫⏫
MPHASIS 2300 CE 84⏫⏫⏫
MPHASIS 2300 CE 83.50⏫⏫⏫
MPHASIS 2300 CE 83⏫⏫⏫
MPHASIS 2300 CE 82.50⏫⏫⏫
Showing the 12 most recent of 20 posts we hold for @stock_cepe07. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“STOCKS OPTIONS KING🫅🏻” (@stock_cepe07), 2,713 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/stock_cepe07.
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.