Telegram RegisterThe public register of Telegram

Channel

و ذكُر ربَّك💗

@YIUIYI

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

51subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001430044685
TypeChannel
Username@YIUIYI
Description‏﴿ والباقِيَاتُ الصّالِحاتُ خيرٌ عند ربكَ ثواباً وخيرٌ أَملاً ﴾
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/YIUIYI

Growth

516 August 2026 — 51 subscribers10 August 2026 — 51 subscribers6 August 202610 August 2026
2 measurements spanning 4 days. 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 50–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 10:4651no change
6 Aug 2026, 16:2951first reading

Engagement

20 posts held, back to 3 March 2022the 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 10 September 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Videos
2
Links
5

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

10 Sept 2023, 20:07 UTC176 viewsread 10 August 2026

- موضوع اليوم: كن أنت الجليس الصالح!❤️

10 Sept 2023, 18:50 UTC174 viewsread 10 August 2026

- أحد أفضل القنوات الدينية ، والمواضيع الشِيقة ، والمنشورات الجميلة ، مكانك هِنا 🖤.

10 Sept 2023, 18:49 UTC156 viewsread 10 August 2026
Forwarded from @ibreeze1

⁃ لسته إقتباسات للقنوات الدينية والمُحافظة. =نّ @Coo1i =إقتباسات @q700as https://t.me/q700as ⁃ - - - - - - - - - - - - - - - - - - - - - - • مُ @lln30 • ظِل @llS8l • أبي @djkth • يَقين @ili_x7 • ﷺ @FHM81 • عَبق @ofjdkc • دار @q600as • وذَكــر @eggsj • كُنوز @rehaon • بَرّيد @massge0 • رحمَة @rhma2a • نافـــذة @Viooxr • فـذكر @foofa66 • مُشرقة @ragiigd • فَلَق @hmshalo • ذكر وأجر @thkr0 • ذِكر @reemyy73 •

8 Sept 2023, 14:36 UTC102 viewsread 10 August 2026

- موضوع اليوم: أسرار الفوز بساعة الإجابة يوم الجمعة!❤️

6 Sept 2023, 19:19 UTC95 viewsread 10 August 2026

- أخطر أربعة أمور تمنع إجابة الدعاء.

6 Sept 2023, 17:38 UTC91 viewsread 10 August 2026

- أحد أفضل القنوات الدينية ، والمواضيع الشِيقة ، والمنشورات الجميلة ، مكانك هِنا 🖤.

6 Sept 2023, 17:38 UTC15 viewsread 10 August 2026
Forwarded from @ibreeze1

⁃ لسته إقتباسات للقنوات الدينية والمُحافظة. =نّ @Coo1i =إقتباسات @q700as https://t.me/q700as ⁃ - - - - - - - - - - - - - - - - - - - - - - • مُ @lln30 • ظِل @llS8l • أبي @djkth • يَقين @ili_x7 • ﷺ @FHM81 • عَبق @ofjdkc • دار @q600as • وذَكــر @eggsj • كُنوز @rehaon • بَرّيد @massge0 • رحمَة @rhma2a • نافـــذة @Viooxr • فـذكر @foofa66 • مُشرقة @ragiigd • فَلَق @hmshalo • ذكر وأجر @thkr0 • ذِكر @reemyy73 •

5 Sept 2023, 18:46 UTC57 viewsread 10 August 2026

- موضوع اليوم: قواعد مهمة عند الدعاء! ❤️

4 Sept 2023, 03:30 UTC70 viewsread 10 August 2026

- أحد أفضل القنوات الدينية ، والمواضيع الشِيقة ، والمنشورات الجميلة ، مكانك هِنا 🖤.

3 Sept 2023, 19:31 UTC60 viewsread 10 August 2026

- موضوع اليوم: طريقة صلاة الوتر.❤️

16 Mar 2022, 23:32 UTC177 viewsread 10 August 2026

-اللهُم صلِّ وسلم وبارك على سيدنا محمد 💚.

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

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.

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

“و ذكُر ربَّك💗” (@YIUIYI), 51 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/YIUIYI.

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.