Channel
๐๐๐บ๐ถ๐ป๐ผ๐๐ ๐๐ถ๐๐ต ๐ฃ๐ฎ๐ถ ๐ฏ
@luminouswithpai
On this record: Topic ยท Growth ยท Engagement ยท Telegram's recommendations ยท Cite this entry
4,747subscribers
-146 since we began measuring on 28 August 2026
Risers and fallers across the register ยท movement among entries of 3,162โ10,000.
Register entry
| Telegram ID | -1002011544350 |
|---|---|
| Type | Channel |
| Username | @luminouswithpai |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/luminouswithpai |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 8 Nov 2026, 11:08 | 4,747 | -8 |
| 5 Nov 2026, 09:56 | 4,755 | -4 |
| 2 Nov 2026, 06:35 | 4,759 | -9 |
| 29 Oct 2026, 23:36 | 4,768 | -1 |
| 26 Oct 2026, 18:00 | 4,769 | -9 |
| 23 Oct 2026, 20:19 | 4,778 | -13 |
| 21 Oct 2026, 02:20 | 4,791 | -3 |
| 18 Oct 2026, 08:35 | 4,794 | -2 |
| 15 Oct 2026, 04:37 | 4,796 | -4 |
| 12 Oct 2026, 04:57 | 4,800 | -8 |
| 5 Oct 2026, 22:56 | 4,808 | -16 |
| 28 Sept 2026, 04:37 | 4,824 | -24 |
| 18 Sept 2026, 09:19 | 4,848 | -7 |
| 14 Sept 2026, 02:58 | 4,855 | -7 |
| 10 Sept 2026, 17:15 | 4,862 | -9 |
| 5 Sept 2026, 08:01 | 4,871 | -7 |
| 1 Sept 2026, 22:54 | 4,878 | no change |
| 1 Sept 2026, 13:56 | 4,878 | -10 |
| 29 Aug 2026, 17:18 | 4,888 | -5 |
| 28 Aug 2026, 21:30 | 4,893 | 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.
@thelapyae_official ยท 28,869
Telegram ranks this channel #24 of 57 here โ alongside 56 others โ read 8 September 2026
@pikasharingfreeforall ยท 20,269
Telegram ranks this channel #26 of 52 here โ alongside 51 others โ read 27 September 2026
@thejournalopportunity ยท 42,804
Telegram ranks this channel #42 of 56 here โ alongside 55 others โ read 28 August 2026
This channel appears in 3 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 8 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐บ๐ถ๐ป๐ผ๐๐ ๐๐ถ๐๐ต ๐ฃ๐ฎ๐ถ ๐ฏโ (@luminouswithpai), 4,747 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/luminouswithpai.
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.