Channel
SM - TNUSRB SI/PC
@SMTNUSRB
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
6,074subscribers
+41 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001642143131 |
|---|---|
| Type | Channel |
| Username | @SMTNUSRB |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/SMTNUSRB |
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 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, 18:17 | 6,074 | -1 |
| 11 Sept 2026, 03:41 | 6,075 | +7 |
| 5 Sept 2026, 20:16 | 6,068 | +1 |
| 2 Sept 2026, 05:03 | 6,067 | +5 |
| 30 Aug 2026, 04:26 | 6,062 | -3 |
| 29 Aug 2026, 18:28 | 6,065 | no change |
| 27 Aug 2026, 14:26 | 6,065 | +6 |
| 24 Aug 2026, 22:33 | 6,059 | +1 |
| 21 Aug 2026, 07:56 | 6,058 | +13 |
| 18 Aug 2026, 04:42 | 6,045 | +10 |
| 14 Aug 2026, 22:27 | 6,035 | +2 |
| 14 Aug 2026, 13:45 | 6,033 | 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.
@Thangamuthuipsacademy786 · 128,156
Telegram ranks this channel #2 of 75 here — alongside 74 others — read 14 August 2026
@tnpscworld1 · 22,945
Telegram ranks this channel #12 of 49 here — alongside 48 others — read 19 September 2026
@krishobaofficial · 112,884
Telegram ranks this channel #26 of 81 here — alongside 80 others — read 14 August 2026
@saisdailyupdate · 24,766
Telegram ranks this channel #37 of 79 here — alongside 78 others — read 15 September 2026
@Rajajiagaramtnpscmain · 49,963
Telegram ranks this channel #55 of 79 here — alongside 78 others — read 25 August 2026
@arivarkacademy · 37,465
Telegram ranks this channel #56 of 82 here — alongside 81 others — read 31 August 2026
This channel appears in 6 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.
“SM - TNUSRB SI/PC” (@SMTNUSRB), 6,074 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/SMTNUSRB.
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.