Channel
Guide To Investing
@guidetoinvesting
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,020subscribers
-144 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001204042096 |
|---|---|
| Type | Channel |
| Username | @guidetoinvesting |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/guidetoinvesting |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 30 Oct 2026, 23:56 | 7,020 | -7 |
| 28 Oct 2026, 03:08 | 7,027 | -4 |
| 25 Oct 2026, 09:46 | 7,031 | -6 |
| 22 Oct 2026, 08:38 | 7,037 | -6 |
| 19 Oct 2026, 11:07 | 7,043 | -12 |
| 16 Oct 2026, 04:27 | 7,055 | -16 |
| 13 Oct 2026, 06:07 | 7,071 | -7 |
| 7 Oct 2026, 08:59 | 7,078 | -16 |
| 30 Sept 2026, 04:20 | 7,094 | -14 |
| 19 Sept 2026, 17:01 | 7,108 | -15 |
| 15 Sept 2026, 08:59 | 7,123 | -5 |
| 11 Sept 2026, 16:02 | 7,128 | -4 |
| 7 Sept 2026, 03:40 | 7,132 | -11 |
| 2 Sept 2026, 11:38 | 7,143 | -8 |
| 30 Aug 2026, 21:28 | 7,151 | -11 |
| 27 Aug 2026, 17:33 | 7,162 | -2 |
| 27 Aug 2026, 11:32 | 7,164 | 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.
@ScienceSpl · 25,053
Telegram ranks this channel #17 of 71 here — alongside 70 others — read 13 September 2026
@helpofstockmarket77 · 27,560
Telegram ranks this channel #23 of 77 here — alongside 76 others — read 9 September 2026
@raghavsvi · 27,460
Telegram ranks this channel #53 of 90 here — alongside 89 others — read 9 September 2026
@AnandBhaav · 30,715
Telegram ranks this channel #74 of 84 here — alongside 83 others — read 6 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Guide To Investing” (@guidetoinvesting), 7,020 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/guidetoinvesting.
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.