Telegram RegisterThe public register of Telegram
Telegram profile photo for محمد مختاری

Channel

محمد مختاری

@mohammadmokhtary77

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

2,848subscribers

+78 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001905385691
TypeChannel
Username@mohammadmokhtary77
CreatedBetween 1 March 2023 and 31 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/mohammadmokhtary77

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 99% 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 why it has no browse page of its own yet.

Growth

2,7682,8482,8087 August 2026 — 2,770 subscribers8 August 2026 — 2,768 subscribers11 August 2026 — 2,769 subscribers14 August 2026 — 2,793 subscribers17 August 2026 — 2,789 subscribers20 August 2026 — 2,792 subscribers23 August 2026 — 2,798 subscribers27 August 2026 — 2,800 subscribers30 August 2026 — 2,809 subscribers2 September 2026 — 2,822 subscribers5 September 2026 — 2,828 subscribers10 September 2026 — 2,831 subscribers12 September 2026 — 2,831 subscribers14 September 2026 — 2,839 subscribers18 September 2026 — 2,848 subscribers7 August 202618 September 2026
15 measurements spanning 42 days, net +78. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,756–2,860 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 01:582,848+9
14 Sept 2026, 06:172,839+8
12 Sept 2026, 23:292,831no change
10 Sept 2026, 17:402,831+3
5 Sept 2026, 20:012,828+6
2 Sept 2026, 03:332,822+13
30 Aug 2026, 07:372,809+9
27 Aug 2026, 02:042,800+2
23 Aug 2026, 21:442,798+6
20 Aug 2026, 08:332,792+3
17 Aug 2026, 12:422,789-4
14 Aug 2026, 00:282,793+24
11 Aug 2026, 04:182,769+1
8 Aug 2026, 00:432,768-2
7 Aug 2026, 12:152,770first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 5 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

صدای بهشت استاد عبدالباسط
@abdulbasetquran · 62,527
Telegram ranks this channel #22 of 81 here — alongside 80 others — read 21 August 2026
ترانه های نوستالژی
@NOSTALGYSONGS · 44,563
Telegram ranks this channel #35 of 84 here — alongside 83 others — read 28 August 2026
داریوش نقطه عطف صدا
@Dariush0Atfsdaa · 44,129
Telegram ranks this channel #38 of 85 here — alongside 84 others — read 28 August 2026

This channel appears in 3 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“محمد مختاری” (@mohammadmokhtary77), 2,848 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mohammadmokhtary77.

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.