Telegram RegisterThe public register of Telegram
Telegram profile photo for Moqlagh | مُغلَق

Channel

Moqlagh | مُغلَق

@moqlagh

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

3,468subscribers

-30 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001029114588
TypeChannel
Username@moqlagh
Description💠 آدرس صفحه‌ی اینستاگرام کانال 👇 instagram.com/Moqlagh
CreatedBetween 1 January 2016 and 30 April 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 September 2026
Last confirmed live8 September 2026
Measurements held12
On Telegramt.me/moqlagh

Growth

3,4683,4983,4835 August 2026 — 3,498 subscribers6 August 2026 — 3,497 subscribers10 August 2026 — 3,491 subscribers13 August 2026 — 3,488 subscribers16 August 2026 — 3,481 subscribers19 August 2026 — 3,480 subscribers23 August 2026 — 3,481 subscribers26 August 2026 — 3,480 subscribers30 August 2026 — 3,478 subscribers2 September 2026 — 3,470 subscribers5 September 2026 — 3,468 subscribers8 September 2026 — 3,468 subscribers5 August 20268 September 2026
12 measurements spanning 34 days, net -30. 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 3,464–3,503 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 13:353,468no change
5 Sept 2026, 21:203,468-2
2 Sept 2026, 03:053,470-8
30 Aug 2026, 06:113,478-2
26 Aug 2026, 21:023,480-1
23 Aug 2026, 12:123,481+1
19 Aug 2026, 15:523,480-1
16 Aug 2026, 15:143,481-7
13 Aug 2026, 01:483,488-3
10 Aug 2026, 01:213,491-6
6 Aug 2026, 15:013,497-1
5 Aug 2026, 19:043,498first 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

ترانه نوشت TaraneNevesht
@taranenevesht · 34,373
Telegram ranks this channel #12 of 95 here — alongside 94 others — read 3 September 2026
Mehryadk
@mehryadk · 67,139
Telegram ranks this channel #16 of 90 here — alongside 89 others — read 20 August 2026
[ جانان ... ]
@Official_JaNaN · 44,084
Telegram ranks this channel #22 of 72 here — alongside 71 others — read 28 August 2026
آهنگ قدیمی | نوستالژی | سمفونی
@SamFoni · 51,448
Telegram ranks this channel #49 of 68 here — alongside 67 others — read 25 August 2026
HISTOGRAPHY
@HISTOGRAPHY · 31,784
Telegram ranks this channel #57 of 91 here — alongside 90 others — read 5 September 2026
Freely
@Freely · 50,833
Telegram ranks this channel #62 of 87 here — alongside 86 others — read 25 August 2026
MohsenChavoshi FC
@mohsenchavoshifc · 48,224
Telegram ranks this channel #70 of 93 here — alongside 92 others — read 26 August 2026
Mohsen Chavoshi
@mohsenchavoshi · 241,149
Telegram ranks this channel #74 of 91 here — alongside 90 others — read 14 August 2026
عرفان طهماسبی
@Erfancnl · 109,448
Telegram ranks this channel #80 of 88 here — alongside 87 others — read 14 August 2026

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

“Moqlagh | مُغلَق” (@moqlagh), 3,468 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/moqlagh.

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.