Channel
MathsGuru
@bulabule
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,756subscribers
+132 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 | -1001321463376 |
|---|---|
| Type | Channel |
| Username | @bulabule |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/bulabule |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 12 Sept 2026, 08:56 | 5,756 | -2 |
| 8 Sept 2026, 15:39 | 5,758 | +3 |
| 3 Sept 2026, 07:57 | 5,755 | +12 |
| 30 Aug 2026, 21:13 | 5,743 | +9 |
| 30 Aug 2026, 11:53 | 5,734 | no change |
| 28 Aug 2026, 07:48 | 5,734 | +21 |
| 25 Aug 2026, 05:03 | 5,713 | +8 |
| 22 Aug 2026, 13:23 | 5,705 | +38 |
| 19 Aug 2026, 06:35 | 5,667 | +28 |
| 16 Aug 2026, 03:35 | 5,639 | +17 |
| 12 Aug 2026, 08:23 | 5,622 | -2 |
| 11 Aug 2026, 19:01 | 5,624 | 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.
@Mahitivedhikegovindareddy · 33,498
Telegram ranks this channel #27 of 62 here — alongside 61 others — read 4 September 2026
@UPSC_SSC_Railway_Current_Affairs · 189,680
Telegram ranks this channel #33 of 58 here — alongside 57 others — read 11 August 2026
@GurukulCareerAcademyDharwad · 40,102
Telegram ranks this channel #42 of 57 here — alongside 56 others — read 30 August 2026
@pariksha_vedike · 31,448
Telegram ranks this channel #46 of 66 here — alongside 65 others — read 6 September 2026
@cetfighters1 · 27,485
Telegram ranks this channel #48 of 57 here — alongside 56 others — read 10 September 2026
@SCIENCE_UPSC_SSC_ALL · 189,594
Telegram ranks this channel #68 of 68 here — alongside 67 others — read 11 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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“MathsGuru” (@bulabule), 5,756 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/bulabule.
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.