Channel
BugLearn
@bugLearn
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,269subscribers
-9 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001995293074 |
|---|---|
| Type | Channel |
| Username | @bugLearn |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/bugLearn |
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 54% 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 |
|---|---|---|
| 14 Sept 2026, 20:17 | 3,269 | +13 |
| 11 Sept 2026, 02:17 | 3,256 | -9 |
| 9 Sept 2026, 21:17 | 3,265 | no change |
| 5 Sept 2026, 20:39 | 3,265 | +1 |
| 2 Sept 2026, 04:34 | 3,264 | -2 |
| 29 Aug 2026, 18:38 | 3,266 | +2 |
| 26 Aug 2026, 23:44 | 3,264 | -2 |
| 24 Aug 2026, 01:14 | 3,266 | -6 |
| 20 Aug 2026, 08:57 | 3,272 | -2 |
| 17 Aug 2026, 11:08 | 3,274 | -4 |
| 16 Aug 2026, 03:30 | 3,278 | 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.
@Pakage_Bargh · 24,069
Telegram ranks this channel #17 of 50 here — alongside 49 others — read 17 September 2026
@faketic · 23,361
Telegram ranks this channel #19 of 53 here — alongside 52 others — read 18 September 2026
@jadi_fans · 43,703
Telegram ranks this channel #34 of 75 here — alongside 74 others — read 28 August 2026
@GoldPackFree_Packs · 32,840
Telegram ranks this channel #41 of 49 here — alongside 48 others — read 9 September 2026
@AOrgan · 47,423
Telegram ranks this channel #41 of 63 here — alongside 62 others — read 24 August 2026
@Black_Security · 63,929
Telegram ranks this channel #42 of 64 here — alongside 63 others — read 21 August 2026
@jozve_iq · 96,872
Telegram ranks this channel #57 of 85 here — alongside 84 others — read 16 August 2026
@Netwo0rk · 52,767
Telegram ranks this channel #61 of 63 here — alongside 62 others — read 24 August 2026
This channel appears in 8 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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“BugLearn” (@bugLearn), 3,269 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/bugLearn.
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.