Channel
777
@QMQ_777
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,005subscribers
+346 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001982897709 |
|---|---|
| Type | Channel |
| Username | @QMQ_777 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/QMQ_777 |
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 97% 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 |
|---|---|---|
| 5 Nov 2026, 05:51 | 4,005 | -15 |
| 2 Nov 2026, 14:58 | 4,020 | -16 |
| 30 Oct 2026, 19:47 | 4,036 | -2 |
| 27 Oct 2026, 23:59 | 4,038 | -4 |
| 21 Oct 2026, 22:48 | 4,042 | +3 |
| 18 Oct 2026, 19:19 | 4,039 | +210 |
| 15 Oct 2026, 14:31 | 3,829 | +134 |
| 12 Oct 2026, 14:16 | 3,695 | +17 |
| 6 Oct 2026, 07:37 | 3,678 | +17 |
| 29 Sept 2026, 07:57 | 3,661 | -36 |
| 12 Sept 2026, 07:57 | 3,697 | +17 |
| 7 Sept 2026, 18:39 | 3,680 | +10 |
| 7 Sept 2026, 00:32 | 3,670 | no change |
| 30 Aug 2026, 18:23 | 3,670 | +7 |
| 28 Aug 2026, 02:13 | 3,663 | +2 |
| 25 Aug 2026, 08:17 | 3,661 | +2 |
| 25 Aug 2026, 04:30 | 3,659 | 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.
@musicc_444 · 46,709
Telegram ranks this channel #1 of 26 here — alongside 25 others — read 12 September 2026
@tojmusic · 20,177
Telegram ranks this channel #6 of 26 here — alongside 25 others — read 29 September 2026
@showbusiness_tj · 20,422
Telegram ranks this channel #17 of 29 here — alongside 28 others — read 28 September 2026
@realshahloi_gul · 50,751
Telegram ranks this channel #38 of 48 here — alongside 47 others — read 25 August 2026
@varzishtvofficial · 51,065
Telegram ranks this channel #65 of 65 here — alongside 64 others — read 26 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“777” (@QMQ_777), 4,005 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/QMQ_777.
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.