
Channel
Mi A3 | G-Cam
@mia3f1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,388subscribers
-58 since we began measuring on 19 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001438560743 |
|---|---|
| Type | Channel |
| Username | @mia3f1 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/mia3f1 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 |
|---|---|---|
| 4 Nov 2026, 21:06 | 2,388 | -4 |
| 2 Nov 2026, 00:54 | 2,392 | +2 |
| 30 Oct 2026, 09:48 | 2,390 | -2 |
| 27 Oct 2026, 15:09 | 2,392 | -3 |
| 24 Oct 2026, 20:20 | 2,395 | +1 |
| 21 Oct 2026, 15:27 | 2,394 | -4 |
| 18 Oct 2026, 04:48 | 2,398 | -4 |
| 15 Oct 2026, 06:26 | 2,402 | -3 |
| 12 Oct 2026, 14:57 | 2,405 | -1 |
| 6 Oct 2026, 06:55 | 2,406 | -11 |
| 29 Sept 2026, 04:35 | 2,417 | -9 |
| 19 Sept 2026, 05:39 | 2,426 | -2 |
| 16 Sept 2026, 01:55 | 2,428 | no change |
| 15 Sept 2026, 06:19 | 2,428 | -3 |
| 11 Sept 2026, 05:41 | 2,431 | -3 |
| 6 Sept 2026, 10:57 | 2,434 | -2 |
| 2 Sept 2026, 12:24 | 2,436 | -1 |
| 30 Aug 2026, 19:35 | 2,437 | -1 |
| 27 Aug 2026, 17:45 | 2,438 | -2 |
| 24 Aug 2026, 14:35 | 2,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.
@gcamlm · 71,020
Telegram ranks this channel #6 of 60 here — alongside 59 others — read 7 September 2026
@Channel_MGC_BSG · 42,734
Telegram ranks this channel #9 of 58 here — alongside 57 others — read 7 September 2026
@Rajasthan_Police_SI_Vdo_Cet · 44,891
Telegram ranks this channel #55 of 62 here — alongside 61 others — read 26 August 2026
@thozhilvaartha_pdf · 47,837
Telegram ranks this channel #57 of 64 here — alongside 63 others — read 27 August 2026
@gurudeviaskas · 76,537
Telegram ranks this channel #70 of 70 here — alongside 69 others — read 19 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Mi A3 | G-Cam” (@mia3f1), 2,388 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/mia3f1.
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.