Telegram RegisterThe public register of Telegram
Telegram profile photo for القرآن الکریم

Channel

القرآن الکریم

@krannnn

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

28,171subscribers

-183 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001174922101
TypeChannel
Username@krannnn
Created14 July 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded14 August 2026
Last confirmed live6 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/krannnn

Growth

28,17128,35428,262.55 August 2026 — 28,354 subscribers6 August 2026 — 28,341 subscribers7 August 2026 — 28,326 subscribers8 August 2026 — 28,329 subscribers9 August 2026 — 28,315 subscribers10 August 2026 — 28,322 subscribers11 August 2026 — 28,312 subscribers12 August 2026 — 28,313 subscribers13 August 2026 — 28,296 subscribers14 August 2026 — 28,296 subscribers15 August 2026 — 28,287 subscribers16 August 2026 — 28,283 subscribers17 August 2026 — 28,281 subscribers18 August 2026 — 28,270 subscribers19 August 2026 — 28,283 subscribers20 August 2026 — 28,273 subscribers21 August 2026 — 28,258 subscribers23 August 2026 — 28,255 subscribers25 August 2026 — 28,230 subscribers25 August 2026 — 28,227 subscribers26 August 2026 — 28,243 subscribers27 August 2026 — 28,233 subscribers28 August 2026 — 28,218 subscribers29 August 2026 — 28,228 subscribers30 August 2026 — 28,239 subscribers31 August 2026 — 28,222 subscribers1 September 2026 — 28,214 subscribers2 September 2026 — 28,200 subscribers4 September 2026 — 28,194 subscribers6 September 2026 — 28,171 subscribers5 August 20266 September 2026
30 measurements spanning 32 days, net -183. 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 28,144–28,381 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
6 Sept 2026, 18:1528,171-23
4 Sept 2026, 06:5628,194-6
2 Sept 2026, 21:3628,200-14
1 Sept 2026, 20:1428,214-8
31 Aug 2026, 17:0728,222-17
30 Aug 2026, 15:0428,239+11
29 Aug 2026, 15:3428,228+10
28 Aug 2026, 17:5728,218-15
27 Aug 2026, 19:4828,233-10
26 Aug 2026, 20:5928,243+16
25 Aug 2026, 22:1328,227-3
25 Aug 2026, 00:4328,230-25
23 Aug 2026, 11:1628,255-3
21 Aug 2026, 19:4928,258-15
20 Aug 2026, 19:3828,273-10
19 Aug 2026, 17:0428,283+13
18 Aug 2026, 18:1428,270-11
17 Aug 2026, 19:2828,281-2
16 Aug 2026, 18:1328,283-4
15 Aug 2026, 03:1428,287first reading

Engagement

No public post preview. We read this entry on 14 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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 7 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.

القرآن و الرقية MP3🔰
@Moshaf_mp3 · 31,969
Telegram ranks this channel #16 of 84 here — alongside 83 others — read 5 September 2026
حفظ القُرآن بـــ التكرار 📘✅
@hifzqurani · 85,404
Telegram ranks this channel #41 of 97 here — alongside 96 others — read 18 August 2026
القرآن الكريم Surah Quran
@qu2an · 96,227
Telegram ranks this channel #45 of 87 here — alongside 86 others — read 19 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“القرآن الکریم” (@krannnn), 28,171 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/krannnn.

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.