Channel
MIYAGI & PANDA 🖤
@miyagi_xcho_mx
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,339subscribers
-136 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001696103510 |
|---|---|
| Type | Channel |
| Username | @miyagi_xcho_mx |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/miyagi_xcho_mx |
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 |
|---|---|---|
| 6 Nov 2026, 14:55 | 4,339 | -4 |
| 4 Nov 2026, 00:26 | 4,343 | -8 |
| 31 Oct 2026, 14:50 | 4,351 | -11 |
| 28 Oct 2026, 13:14 | 4,362 | -4 |
| 25 Oct 2026, 17:35 | 4,366 | -3 |
| 22 Oct 2026, 19:56 | 4,369 | -2 |
| 19 Oct 2026, 16:10 | 4,371 | -5 |
| 16 Oct 2026, 12:20 | 4,376 | -9 |
| 13 Oct 2026, 18:16 | 4,385 | -9 |
| 8 Oct 2026, 05:36 | 4,394 | -6 |
| 1 Oct 2026, 13:59 | 4,400 | -14 |
| 16 Sept 2026, 01:01 | 4,414 | +7 |
| 11 Sept 2026, 23:39 | 4,407 | +3 |
| 7 Sept 2026, 16:40 | 4,404 | -16 |
| 3 Sept 2026, 22:11 | 4,420 | no change |
| 2 Sept 2026, 23:56 | 4,420 | -1 |
| 30 Aug 2026, 16:14 | 4,421 | -6 |
| 27 Aug 2026, 22:22 | 4,427 | -5 |
| 25 Aug 2026, 01:28 | 4,432 | -8 |
| 22 Aug 2026, 00:22 | 4,440 | 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.
@MarketingQui · 145,420
Telegram ranks this channel #9 of 62 here — alongside 61 others — read 12 August 2026
@nashidy_v · 135,774
Telegram ranks this channel #13 of 52 here — alongside 51 others — read 13 August 2026
@oimaskva · 31,597
Telegram ranks this channel #19 of 51 here — alongside 50 others — read 9 September 2026
@music_muzyka_2025 · 262,784
Telegram ranks this channel #22 of 56 here — alongside 55 others — read 30 August 2026
@muscarx · 294,642
Telegram ranks this channel #23 of 51 here — alongside 50 others — read 10 August 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“MIYAGI & PANDA 🖤” (@miyagi_xcho_mx), 4,339 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/miyagi_xcho_mx.
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.