Telegram RegisterThe public register of Telegram
Telegram profile photo for Mirjalol | Official

Channel

Mirjalol | Official

@Mirjalol

Has discussion group

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

4,043subscribers

-167 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001169411543
TypeChannel
Username@Mirjalol
DescriptionOwner @Aligrach ▪️ 𝐒𝐢𝐧𝐠𝐞𝐫 ▪️ 𝐂𝐨𝐦𝐩𝐨𝐬𝐞𝐫 Official ❌ FAN CLUB✅ Rasmiy YouTube kanali↩️ youtube.com/@mirjalolnematov Fan Club @mirjalol Official ✅
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live5 September 2026
Measurements held12
On Telegramt.me/Mirjalol

Growth

4,0434,2104,126.57 August 2026 — 4,210 subscribers8 August 2026 — 4,199 subscribers11 August 2026 — 4,181 subscribers14 August 2026 — 4,184 subscribers17 August 2026 — 4,169 subscribers20 August 2026 — 4,149 subscribers23 August 2026 — 4,108 subscribers26 August 2026 — 4,103 subscribers29 August 2026 — 4,085 subscribers1 September 2026 — 4,062 subscribers5 September 2026 — 4,043 subscribers5 September 2026 — 4,043 subscribers7 August 20265 September 2026
12 measurements spanning 29 days, net -167. 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 4,018–4,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 12:564,043no change
5 Sept 2026, 08:384,043-19
1 Sept 2026, 15:384,062-23
29 Aug 2026, 11:494,085-18
26 Aug 2026, 19:544,103-5
23 Aug 2026, 19:544,108-41
20 Aug 2026, 08:254,149-20
17 Aug 2026, 13:264,169-15
14 Aug 2026, 12:574,184+3
11 Aug 2026, 07:464,181-18
8 Aug 2026, 01:274,199-11
7 Aug 2026, 04:114,210first 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.

فال قهوه و تاروت ثمین
@saminfalll · 66,128
Telegram ranks this channel #57 of 62 here — alongside 61 others — read 20 August 2026
♻️☕ فال قهوه و کائنات☕♻️
@ghahve_kaenat · 105,690
Telegram ranks this channel #61 of 61 here — alongside 60 others — read 15 August 2026
چشم سوّم 👁 ارتباط با کائنات
@Cheshm3kaenat · 29,086
Telegram ranks this channel #82 of 83 here — alongside 82 others — read 9 September 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Mirjalol | Official” (@Mirjalol), 4,043 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Mirjalol.

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.