Channel
Notes & Legal Updates.
@ballbba
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,142subscribers
+196 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001716649503 |
|---|---|
| Type | Channel |
| Username | @ballbba |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/ballbba |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 19 Sept 2026, 11:21 | 4,142 | +19 |
| 15 Sept 2026, 05:21 | 4,123 | +26 |
| 11 Sept 2026, 16:36 | 4,097 | +31 |
| 7 Sept 2026, 05:14 | 4,066 | +18 |
| 5 Sept 2026, 12:54 | 4,048 | no change |
| 2 Sept 2026, 14:37 | 4,048 | +20 |
| 30 Aug 2026, 22:58 | 4,028 | +25 |
| 27 Aug 2026, 20:28 | 4,003 | +14 |
| 25 Aug 2026, 05:13 | 3,989 | +13 |
| 21 Aug 2026, 19:38 | 3,976 | +14 |
| 18 Aug 2026, 19:36 | 3,962 | -2 |
| 15 Aug 2026, 17:14 | 3,964 | +12 |
| 12 Aug 2026, 01:36 | 3,952 | +6 |
| 11 Aug 2026, 07:30 | 3,946 | 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.
@IndianLawBooks · 26,047
Telegram ranks this channel #3 of 65 here — alongside 64 others — read 13 September 2026
@English_Grammar_Mock_Test_Quiz · 33,291
Telegram ranks this channel #35 of 53 here — alongside 52 others — read 4 September 2026
@universitychampion · 22,990
Telegram ranks this channel #36 of 51 here — alongside 50 others — read 19 September 2026
@SSC_Quiz_daily · 220,322
Telegram ranks this channel #37 of 78 here — alongside 77 others — read 11 August 2026
@theshubhamsir · 29,316
Telegram ranks this channel #42 of 73 here — alongside 72 others — read 8 September 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Notes & Legal Updates.” (@ballbba), 4,142 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ballbba.
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.