Telegram RegisterThe public register of Telegram
Telegram profile photo for قرآن مراسم ترحیم

Channel

قرآن مراسم ترحیم

@quran_4mazar

On this record: Growth · Engagement · Posts · Cite this entry

81subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002018483403
TypeChannel
Username@quran_4mazar
CreatedBetween 1 November 2023 and 11 February 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/quran_4mazar

Growth

7783807 August 2026 — 77 subscribers9 August 2026 — 77 subscribers15 August 2026 — 80 subscribers22 August 2026 — 81 subscribers29 August 2026 — 83 subscribers16 September 2026 — 81 subscribers817 August 202616 September 2026
6 measurements spanning 40 days, net +4. 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 76–84 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 02:3981-2
29 Aug 2026, 19:4683+2
22 Aug 2026, 06:4881+1
15 Aug 2026, 00:1880+3
9 Aug 2026, 20:3077no change
7 Aug 2026, 14:1377first reading

Engagement

20 posts held, back to 11 February 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Feb 2024, 07:07 UTC961 viewsread 9 August 2026
File

سوره های مبارکه بلد و شمس تمام آیات

11 Feb 2024, 07:07 UTC≈1,010 viewsread 9 August 2026
File

سوره مبارکه یوسف آیات 86 الی 100

11 Feb 2024, 07:07 UTC≈1,060 viewsread 9 August 2026
File

سوره مبارکه زمر آیات 69 الی 75 سوره های مبارکه انفطار ضحی شرح فتح تمام آیات

11 Feb 2024, 07:07 UTC782 viewsread 9 August 2026
File

سوره مبارکه قلم تمام آیات سوره مبارکه حاقه آیات 1 الی 18

11 Feb 2024, 07:07 UTC861 viewsread 9 August 2026
File

سوره مبارکه کهف آیات 60 الی 78 سوره های مبارکه ضحی و حمد تمام آیات

11 Feb 2024, 07:06 UTC687 viewsread 9 August 2026
File

سوره مبارکه هود آیات 36 الی 49 سوره مبارکه بلد تمام آیات

11 Feb 2024, 07:06 UTC650 viewsread 9 August 2026
File

سوره مبارکه قمر آیات 49 الی 55 سوره مبارکه الرحمن آیات 1 الی 17 سوره مبارکه نباء آیات 31 الی 40 سوره های مبارکه تکویر ضحی شرح حمد تمام آیات سوره مبارکه بقره آیات 1 الی 5

Showing the 12 most recent of 20 posts we hold for @quran_4mazar. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“قرآن مراسم ترحیم” (@quran_4mazar), 81 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/quran_4mazar.

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.