
Channel
STUDY COMMERCE π¨π»βπ«
@studycommerce
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
3,091subscribers
-66 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 | -1001118331257 |
|---|---|
| Type | Channel |
| Username | @studycommerce |
| Created | Between 1 February 2017 and 31 December 2019 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/studycommerce |
Topic
Education β 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 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 |
|---|---|---|
| 6 Nov 2026, 04:09 | 3,091 | -1 |
| 3 Nov 2026, 01:59 | 3,092 | -2 |
| 31 Oct 2026, 09:06 | 3,094 | -5 |
| 28 Oct 2026, 06:45 | 3,099 | -3 |
| 25 Oct 2026, 12:44 | 3,102 | -2 |
| 22 Oct 2026, 16:21 | 3,104 | +1 |
| 19 Oct 2026, 12:20 | 3,103 | -4 |
| 16 Oct 2026, 15:57 | 3,107 | -4 |
| 13 Oct 2026, 11:06 | 3,111 | -7 |
| 7 Oct 2026, 15:56 | 3,118 | -6 |
| 30 Sept 2026, 21:39 | 3,124 | -12 |
| 16 Sept 2026, 14:58 | 3,136 | -5 |
| 12 Sept 2026, 10:02 | 3,141 | -5 |
| 10 Sept 2026, 14:04 | 3,146 | no change |
| 7 Sept 2026, 21:59 | 3,146 | -5 |
| 2 Sept 2026, 16:05 | 3,151 | -4 |
| 30 Aug 2026, 04:35 | 3,155 | -1 |
| 27 Aug 2026, 04:38 | 3,156 | -4 |
| 24 Aug 2026, 02:12 | 3,160 | +2 |
| 20 Aug 2026, 00:47 | 3,158 | 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.
@UPSC_Quiz_MCQ_PYQ_CSAT_Test_PDF Β· 73,049
Telegram ranks this channel #10 of 64 here β alongside 63 others β read 19 August 2026
@vijayrajcmg Β· 67,800
Telegram ranks this channel #13 of 64 here β alongside 63 others β read 21 August 2026
@mppscadda Β· 19,135
Telegram ranks this channel #18 of 52 here β alongside 51 others β read 1 October 2026
@computer_questions_Latest Β· 42,950
Telegram ranks this channel #31 of 65 here β alongside 64 others β read 28 August 2026
This channel appears in 4 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 6 November 2026 β this entry's latest reading, not the date you are reading this.
βSTUDY COMMERCE π¨π»βπ«β (@studycommerce), 3,091 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/studycommerce.
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.