9 measurements spanning 25 days, net +11. 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,249–1,268 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
31 Aug 2026, 15:12
1,262
+2
28 Aug 2026, 09:33
1,260
-2
25 Aug 2026, 16:33
1,262
-3
22 Aug 2026, 19:26
1,265
-1
19 Aug 2026, 02:02
1,266
+4
13 Aug 2026, 01:28
1,262
+3
9 Aug 2026, 22:12
1,259
+8
6 Aug 2026, 11:51
1,251
no change
6 Aug 2026, 11:04
1,251
first reading
Engagement
17 posts held, back to 21 May 2026 — the 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 17 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
195 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 33.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
65
33.3%
❤🔥
61
31.3%
🔥
42
21.5%
👍
22
11.3%
👨💻
3
1.54%
💯
2
1.03%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 195 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 21 May 2026 to 29 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 17 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Shadow6by8. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 17 most recent posts we hold for this entry, published 21 May 2026 to 29 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
SalatTimes أوقات الصلاة — v1.0 Beta7
SHA256:
08af6c08c961676c5fd55be2a0052d007f27e32c74c579f71e8654961267bb50
Changes:
• Rebuilt all home screen widgets from scratch and added Prayer Grid, Sun View, and Hijri Month Calendar, with previews that follow Material colors and system language.
• Added app shortcuts for quick access via long-press or the widget picker.
• Redesigned Tasbeeh screen with a progress ring and com…
Beta7 will be late for a longer time due to the library refactor from Glance to RemoteView for greater stability. I am also working to add new powerful widgets and shortcuts.
SalatTimes أوقات الصلاة — v1.0 Beta6
SHA256:
9f0141fc43a8887ca8b5df3de5227ed5ce264f7fae773365534f25533b0ee9de
Changes:
• Reduced minSDK to Android 9 (28) and fix some issues to handle it.
• Replaced static moon phase images with dynamic daily calculations.
• Fixed Hijri page layout on high-DPI devices.
• Refined the About page, added icons, and bundled the Privacy Policy for offline access.
• Improved prayer cards wi…
Al-Minshawi المنشاوي — Version 1.3 Stable
SHA256:
415c4f2f87ac114c3039adc417f3a9c9f2e0f8adf27b599af9f148f849abad73
• Fixed a missing permission (by mistake) with Android Auto that caused the app not to work at all and fixed all issues related to Android Auto.
• Removed the player cache limit so nothing gets deleted automatically.
• Switched from byte-array artwork metadata to file-based URI via FileProvider to fix cr…
ShafeeZekr ذكرُ الشفيع — Version 2.1 Hot-fix
SHA256:
83da895ed172e919d142110b5e64fc783e8c6daea11d7f954c09c675727cb09b
• Fixed an issue where the app crashes on devices with no browser or app registered to handle URL intents.
Al-Minshawi المنشاوي — Version 1.2 Update
(This update introduces significant changes)
(goToAPK)
All Changes:
• Added full Android Auto support — browse and play surahs directly from your car's media interface.
• Replaced the guide banner with a dedicated Guide page that explains every feature and option in the app.
• Redesigned the home header with new colors and a custom font for the sheikh's name and description…
ShafeeZekr ذكرُ الشفيع — Version 2.1 Update
SHA256:
dc3f4db67ceb00c662ef6bd29318a3ee1e30963d8caca1c116127a1dbd9b15a3
Changes:
• Improved the "mute during phone calls" feature: it now requests phone state permission to much more accurately detect active calls.
• Added an option to automatically dismiss notifications once the reminder sound finishes playing.
• Added an option to use your device's system volume for remi…
SalatTimes أوقات الصلاة — v1.0 Beta5
SHA256:
2139405c8291739c61c80952f47834a7a036421df3e5e4f8d8580f5767a9f4f9
Changes:
• Refined navigation icons.
• Significant performance optimization (~90%), especially for low-end devices.
• Fixed Hijri events displaying in the wrong language.
• Replaced the custom blue color with a rose color.
• Fixed custom palette compression on large DPI screens.
• Reworked Adhan/Prayer alerts…
❤🔥9❤4
Showing the 12 most recent of 17 posts we hold for @Shadow6by8. 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.
Citation-graph rank
Citation-graph rank — 487,608 of 1,629,497 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 31 August 2026 — this
entry's latest reading, not the date you are reading this.
“Shadow6by8” (@Shadow6by8), 1,262 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Shadow6by8.
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.