Channel
Share Market Infomania Live & #Q1 Quarter Results
@share_market_infomania_live
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,663subscribers
-50 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001505379807 |
|---|---|
| Type | Channel |
| Username | @share_market_infomania_live |
| Created | Between 1 July 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/share_market_infomania_live |
Topic
Other / unclassifiable — 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 45% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:17 | 2,663 | -8 |
| 14 Sept 2026, 14:37 | 2,671 | -4 |
| 14 Sept 2026, 00:50 | 2,675 | no change |
| 11 Sept 2026, 05:39 | 2,675 | -10 |
| 6 Sept 2026, 14:35 | 2,685 | -4 |
| 2 Sept 2026, 01:53 | 2,689 | -7 |
| 30 Aug 2026, 01:16 | 2,696 | -8 |
| 26 Aug 2026, 17:12 | 2,704 | -7 |
| 23 Aug 2026, 17:37 | 2,711 | -3 |
| 19 Aug 2026, 20:05 | 2,714 | +1 |
| 19 Aug 2026, 06:30 | 2,713 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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.
@shorterm1 · 29,448
Telegram ranks this channel #34 of 93 here — alongside 92 others — read 6 September 2026
@gameofcharts · 28,991
Telegram ranks this channel #37 of 81 here — alongside 80 others — read 8 September 2026
@stocksresult · 28,897
Telegram ranks this channel #43 of 93 here — alongside 92 others — read 25 September 2026
@stockupdate9 · 47,634
Telegram ranks this channel #58 of 91 here — alongside 90 others — read 31 August 2026
@aakashkandoi_FR · 106,878
Telegram ranks this channel #83 of 90 here — alongside 89 others — read 19 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Share Market Infomania Live & #Q1 Quarter Results” (@share_market_infomania_live), 2,663 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/share_market_infomania_live.
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.