Channel
BANKING PDF
@BankPdf2
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,407subscribers
-93 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002184236907 |
|---|---|
| Type | Channel |
| Username | @BankPdf2 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/BankPdf2 |
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 70% 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 |
|---|---|---|
| 4 Nov 2026, 04:37 | 3,407 | -5 |
| 1 Nov 2026, 08:11 | 3,412 | -6 |
| 29 Oct 2026, 11:46 | 3,418 | -6 |
| 26 Oct 2026, 15:16 | 3,424 | -4 |
| 23 Oct 2026, 11:30 | 3,428 | -6 |
| 20 Oct 2026, 15:19 | 3,434 | -3 |
| 17 Oct 2026, 08:20 | 3,437 | -8 |
| 14 Oct 2026, 16:40 | 3,445 | -8 |
| 11 Oct 2026, 09:41 | 3,453 | -6 |
| 4 Oct 2026, 17:15 | 3,459 | -23 |
| 24 Sept 2026, 21:21 | 3,482 | -14 |
| 16 Sept 2026, 20:21 | 3,496 | -12 |
| 12 Sept 2026, 12:17 | 3,508 | -9 |
| 8 Sept 2026, 17:55 | 3,517 | -15 |
| 7 Sept 2026, 23:55 | 3,532 | no change |
| 3 Sept 2026, 18:38 | 3,532 | -8 |
| 31 Aug 2026, 00:05 | 3,540 | -1 |
| 28 Aug 2026, 02:12 | 3,541 | +5 |
| 25 Aug 2026, 12:46 | 3,536 | +4 |
| 22 Aug 2026, 12:06 | 3,532 | 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.
@Quant149 · 160,233
Telegram ranks this channel #14 of 59 here — alongside 58 others — read 12 August 2026
@reasoningbysachinsirbanking · 60,147
Telegram ranks this channel #15 of 45 here — alongside 44 others — read 24 August 2026
@gadiscussionchannel · 55,941
Telegram ranks this channel #21 of 75 here — alongside 74 others — read 23 August 2026
@BWSachinSir · 62,063
Telegram ranks this channel #25 of 55 here — alongside 54 others — read 23 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“BANKING PDF” (@BankPdf2), 3,407 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/BankPdf2.
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.