Telegram RegisterThe public register of Telegram

Channel

فَيـض

@QllIY

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

1,175subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001785400173
TypeChannel
Username@QllIY
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/QllIY

Growth

1,17512 Aug 2026, 08:45 — 1,175 subscribers12 Aug 2026, 17:53 — 1,175 subscribers12 Aug 2026, 08:4512 Aug 2026, 17:53
2 measurements taken within a single day. 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 1,174–1,176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:531,175no change
12 Aug 2026, 08:451,175first reading

Engagement

20 posts held, back to 4 June 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 15 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
18s
Average length
18s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

30 Sept 2025, 20:55 UTC≈1,220 viewsread 12 August 2026

لا حول ولا قوة إلا بالله العليّ العظيم

30 Sept 2025, 20:55 UTC≈1,240 viewsread 12 August 2026

‏اللهم اغفر لنا ولوالدينا وللمؤمنين والمؤمنات وافتح لنا أبواب فضلك ورحمتك وعفوك ومغفرتك وآتنا في الدنيا حسنة وفي الآخرة حسنة وقنا عذاب النار

11 Sept 2025, 15:54 UTC≈1,040 viewsread 12 August 2026
Forwarded from @aii8i8

https://ehsan.sa/donationcampaign/details/1889825

9 Sept 2025, 19:12 UTC939 viewsread 12 August 2026

إنا لله وإنا إليه راجعون ، اللهم أغفر لهم وأرحمهم وأعف عنهم وعافهم وأكرم نزلهم ووسع مدخلهم وأغسلهم بماء وثلج وبرد ونقهم من الخطايا كما ينقى الثوب الأبيض من الدنس وقهم فتنة القبر وعذاب النار

9 Sept 2025, 19:12 UTC831 viewsread 12 August 2026
Forwarded from @aii8i8

(إِنَّا لِلّهِ وَإِنَّـا إِلَيْهِ رَاجِعونَ) انتقل إلى رحمة الله أخوي وابنائه إن العين لتدمع وإن القلب ليحزن وإنا على فراقكم لمحزونون ولا نقول إلا ما يرضي ربنا ، رحمهم الله رحمة واسعة وغفر لهم وانار قبورهم واسكنهم فسيح جناته ، وربط على قلوبنا بالصبر والسلوان

Showing the 12 most recent of 20 posts we hold for @QllIY. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

القران كريم, ادعية ، اذكار.
@lmyl_a · 169,896
Telegram ranks this channel #19 of 88 here — alongside 87 others — read 12 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“فَيـض” (@QllIY), 1,175 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/QllIY.

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.