Channel
Miabofy
@Miabofy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,410subscribers
-242 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 | -1001906451046 |
|---|---|
| Type | Channel |
| Username | @Miabofy |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/Miabofy |
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 100% 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 |
|---|---|---|
| 2 Nov 2026, 08:27 | 4,410 | -9 |
| 29 Oct 2026, 23:35 | 4,419 | -8 |
| 27 Oct 2026, 01:26 | 4,427 | -11 |
| 23 Oct 2026, 15:25 | 4,438 | -3 |
| 20 Oct 2026, 07:29 | 4,441 | -10 |
| 17 Oct 2026, 08:04 | 4,451 | -5 |
| 14 Oct 2026, 16:00 | 4,456 | -9 |
| 11 Oct 2026, 03:57 | 4,465 | -15 |
| 4 Oct 2026, 21:02 | 4,480 | -34 |
| 25 Sept 2026, 10:17 | 4,514 | -17 |
| 16 Sept 2026, 23:18 | 4,531 | -19 |
| 12 Sept 2026, 14:59 | 4,550 | -12 |
| 8 Sept 2026, 06:40 | 4,562 | -17 |
| 3 Sept 2026, 08:15 | 4,579 | -8 |
| 2 Sept 2026, 23:07 | 4,587 | no change |
| 31 Aug 2026, 08:33 | 4,587 | -6 |
| 28 Aug 2026, 13:33 | 4,593 | -11 |
| 25 Aug 2026, 10:43 | 4,604 | -4 |
| 22 Aug 2026, 20:43 | 4,608 | -15 |
| 19 Aug 2026, 16:55 | 4,623 | 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.
@miabomusic · 145,435
Telegram ranks this channel #7 of 84 here — alongside 83 others — read 12 August 2026
@remix_rapmusic · 51,764
Telegram ranks this channel #49 of 78 here — alongside 77 others — read 23 August 2026
@phonix_remix · 40,540
Telegram ranks this channel #52 of 80 here — alongside 79 others — read 30 August 2026
@remixrapfars · 29,129
Telegram ranks this channel #66 of 78 here — alongside 77 others — read 7 September 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Miabofy” (@Miabofy), 4,410 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Miabofy.
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.