
Channel
Bank_Buddy 🏦
@Bank_SSR
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,909subscribers
-52 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001147329716 |
|---|---|
| Type | Channel |
| Username | @Bank_SSR |
| Created | Between 1 June 2016 and 31 January 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Bank_SSR |
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 94% 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 |
|---|---|---|
| 15 Sept 2026, 23:17 | 3,909 | -1 |
| 12 Sept 2026, 02:36 | 3,910 | -6 |
| 7 Sept 2026, 16:37 | 3,916 | -19 |
| 5 Sept 2026, 23:08 | 3,935 | no change |
| 2 Sept 2026, 12:33 | 3,935 | -4 |
| 30 Aug 2026, 03:25 | 3,939 | -3 |
| 27 Aug 2026, 11:25 | 3,942 | -4 |
| 24 Aug 2026, 01:25 | 3,946 | -3 |
| 20 Aug 2026, 10:15 | 3,949 | -3 |
| 17 Aug 2026, 20:54 | 3,952 | -8 |
| 14 Aug 2026, 21:35 | 3,960 | -1 |
| 13 Aug 2026, 17:30 | 3,961 | 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.
@SSAShubhamSirAcademy · 48,568
Telegram ranks this channel #18 of 63 here — alongside 62 others — read 26 August 2026
@englishpitara · 25,373
Telegram ranks this channel #26 of 62 here — alongside 61 others — read 14 September 2026
@Studified_Ashish_Arora_pdfs · 53,800
Telegram ranks this channel #28 of 67 here — alongside 66 others — read 24 August 2026
@FutureeBankerss · 37,557
Telegram ranks this channel #29 of 65 here — alongside 64 others — read 1 September 2026
@history_by_Khan_Abhishek_Sir · 134,706
Telegram ranks this channel #45 of 65 here — alongside 64 others — read 13 August 2026
@GaGkByAkshayCholke · 41,107
Telegram ranks this channel #50 of 63 here — alongside 62 others — read 30 August 2026
@navachetana08 · 36,321
Telegram ranks this channel #57 of 68 here — alongside 67 others — read 2 September 2026
This channel appears in 7 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Bank_Buddy 🏦” (@Bank_SSR), 3,909 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Bank_SSR.
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.