
Channel
ππππ°π¬ ππ’ππ°π¬ ππ©πππππ¬π
@OPSC_OSSC_OSSSC_SSB
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
3,175subscribers
-6 since we began measuring on 20 August 2026
Risers and fallers across the register Β· movement among entries of 3,162β10,000.
Register entry
| Telegram ID | -1001790004633 |
|---|---|
| Type | Channel |
| Username | @OPSC_OSSC_OSSSC_SSB |
| Created | Between 1 December 2021 and 30 April 2023 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 2 times, most recently 4 November 2026 |
| On Telegram | t.me/OPSC_OSSC_OSSSC_SSB |
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 85% 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 |
|---|---|---|
| 31 Oct 2026, 21:21 | 3,175 | -6 |
| 29 Oct 2026, 07:59 | 3,181 | -7 |
| 26 Oct 2026, 09:35 | 3,188 | -2 |
| 23 Oct 2026, 00:58 | 3,190 | -2 |
| 16 Oct 2026, 09:15 | 3,192 | +2 |
| 13 Oct 2026, 15:46 | 3,190 | +1 |
| 8 Oct 2026, 00:19 | 3,189 | +2 |
| 1 Oct 2026, 17:02 | 3,187 | +10 |
| 16 Sept 2026, 11:18 | 3,177 | -2 |
| 12 Sept 2026, 13:57 | 3,179 | -1 |
| 10 Sept 2026, 00:47 | 3,180 | no change |
| 8 Sept 2026, 11:19 | 3,180 | +10 |
| 3 Sept 2026, 15:37 | 3,170 | -2 |
| 31 Aug 2026, 00:15 | 3,172 | -6 |
| 24 Aug 2026, 22:27 | 3,178 | -3 |
| 20 Aug 2026, 23:30 | 3,181 | 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.
@OPSCLIBRARY Β· 22,787
Telegram ranks this channel #7 of 68 here β alongside 67 others β read 19 September 2026
@sscelitee Β· 21,200
Telegram ranks this channel #16 of 57 here β alongside 56 others β read 30 September 2026
@TestbookOdishaTeaching Β· 21,186
Telegram ranks this channel #18 of 40 here β alongside 39 others β read 28 September 2026
@Motivational_Vichar_Quotes_Hindi Β· 63,279
Telegram ranks this channel #31 of 73 here β alongside 72 others β read 20 August 2026
@mechjobncareer Β· 37,017
Telegram ranks this channel #56 of 61 here β alongside 60 others β read 31 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 31 October 2026 β this entry's latest reading, not the date you are reading this.
βππππ°π¬ ππ’ππ°π¬ ππ©πππππ¬πβ (@OPSC_OSSC_OSSSC_SSB), 3,175 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/OPSC_OSSC_OSSSC_SSB.
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.