Channel
mow3enx
@namji7
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,877subscribers
-38 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001734622410 |
|---|---|
| Type | Channel |
| Username | @namji7 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/namji7 |
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 15 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 |
|---|---|---|
| 4 Nov 2026, 20:38 | 2,877 | -5 |
| 2 Nov 2026, 01:36 | 2,882 | -4 |
| 30 Oct 2026, 05:37 | 2,886 | -4 |
| 27 Oct 2026, 03:05 | 2,890 | +1 |
| 23 Oct 2026, 23:20 | 2,889 | -4 |
| 21 Oct 2026, 08:08 | 2,893 | +1 |
| 18 Oct 2026, 11:06 | 2,892 | -3 |
| 15 Oct 2026, 17:14 | 2,895 | -4 |
| 12 Oct 2026, 16:17 | 2,899 | -6 |
| 6 Oct 2026, 08:17 | 2,905 | -16 |
| 29 Sept 2026, 13:58 | 2,921 | -5 |
| 16 Sept 2026, 01:39 | 2,926 | -7 |
| 12 Sept 2026, 00:21 | 2,933 | no change |
| 8 Sept 2026, 00:21 | 2,933 | +5 |
| 3 Sept 2026, 07:48 | 2,928 | +5 |
| 31 Aug 2026, 04:54 | 2,923 | +8 |
| 27 Aug 2026, 23:30 | 2,915 | 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.
@taranom_khiyal · 99,755
Telegram ranks this channel #4 of 65 here — alongside 64 others — read 29 August 2026
@musicnab_r · 19,589
Telegram ranks this channel #10 of 62 here — alongside 61 others — read 5 October 2026
@atre_t0_chanel · 59,498
Telegram ranks this channel #16 of 43 here — alongside 42 others — read 27 August 2026
@rivanmusic1 · 19,976
Telegram ranks this channel #43 of 75 here — alongside 74 others — read 27 September 2026
@rezashiriichannel · 35,452
Telegram ranks this channel #61 of 78 here — alongside 77 others — read 4 September 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.
“mow3enx” (@namji7), 2,877 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/namji7.
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.