File, posted without a caption
custom 590219842385923879210custom 52426900851361359309custom 59025292909598538679custom 52427303676344058736custom 59069137997340407076

Channel
@iiNayt
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
64subscribers
+50 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003583796337 |
|---|---|
| Type | Channel |
| Username | @iiNayt |
| Created | 27 July 2026 — measured — dated from the channel’s first post |
| First recorded | 13 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/iiNayt |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
@iiNayt was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:17 | 64 | -4 |
| 8 Nov 2026, 22:36 | 68 | +3 |
| 8 Nov 2026, 01:22 | 65 | +49 |
| 25 Sept 2026, 23:00 | 16 | -2 |
| 13 Sept 2026, 13:22 | 18 | no change |
| 12 Sept 2026, 17:19 | 18 | -1 |
| 4 Sept 2026, 15:17 | 19 | -2 |
| 27 Aug 2026, 13:27 | 21 | -2 |
| 21 Aug 2026, 02:13 | 23 | -5 |
| 13 Aug 2026, 23:46 | 28 | +14 |
| 7 Aug 2026, 03:47 | 14 | first reading |
14 posts held, back to 27 July 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 2 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 14 (27 July 2026 – 6 November 2026) |
| Views total | 845 |
| Reactions total | 86 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 01:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 5 videos 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.
1,328 reactions across 13 posts, in 15 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5244969209531760017 | 271 | 20.4% | |
| custom 5242690085136135930 | 258 | 19.4% | |
| custom 5242730367634405873 | 258 | 19.4% | |
| custom 5823581487047383890 | 221 | 16.6% | |
| custom 5902247669954255312 | 205 | 15.4% | |
| custom 5059972297939485930 | 22 | 1.66% | |
| custom 5974116354150637901 | 22 | 1.66% | |
| custom 5906913799734040707 | 18 | 1.36% | |
| custom 5902529290959853867 | 17 | 1.28% | |
| custom 5902198423859238792 | 13 | 0.979% | |
| custom 5902002302767601391 | 8 | 0.602% | |
| custom 5902426675601216918 | 6 | 0.452% | |
| custom 5902305372839876085 | 4 | 0.301% | |
| custom 5902204037381494503 | 3 | 0.226% | |
| custom 5902273040326071556 | 2 | 0.151% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 13 of the 14 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 1,328 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 27 July 2026 to 6 November 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’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
File, posted without a caption
custom 590219842385923879210custom 52426900851361359309custom 59025292909598538679custom 52427303676344058736custom 59069137997340407076
اللهم يا رب الناس، يا من بيده الشفاء والعافية، اشفه أنت الشافي، لا شفاء إلا شفاؤك، شفاءً لا يغادر سقمًا. اللهم اشفِ جسده، وقوِّ ضعفه، وأرح قلبه، وطمئن نفسه، واجعل في كل لحظة من مرضه لطفًا ورحمةً وأجرًا عظيمًا.
custom 524496920953176001712custom 590691379973404070712custom 59020023027676013918custom 59025292909598538678custom 52427303676344058736
Video, posted without a caption
custom 597411635415063790114custom 52449692095317600176custom 52427303676344058734custom 52426900851361359302custom 59024266756012169182
Sticker, posted without a caption
custom 50599722979394859303custom 52426900851361359303custom 52427303676344058733custom 52449692095317600172custom 59024266756012169182
Video, posted without a caption
custom 58235814870473838908custom 52426900851361359303custom 52427303676344058733custom 52449692095317600172custom 59023053728398760851
Sticker, posted without a caption
custom 50599722979394859302custom 52426900851361359302custom 52427303676344058732custom 59021984238592387922custom 59024266756012169182
Video, posted without a caption
custom 59741163541506379014custom 52449692095317600173custom 52426900851361359302custom 52427303676344058732custom 59023053728398760852
Sticker, posted without a caption
custom 50599722979394859302custom 52426900851361359302custom 52449692095317600172custom 59022040373814945032custom 59022476699542553122
Video, posted without a caption
custom 58235814870473838904custom 52426900851361359302custom 52449692095317600172custom 52427303676344058731custom 59021984238592387921
Sticker, posted without a caption
custom 50599722979394859302custom 52449692095317600172custom 52426900851361359301custom 59022040373814945031custom 59022730403260715561
Video, posted without a caption
custom 59741163541506379014custom 52449692095317600172custom 52426900851361359301custom 59022476699542553121custom 59022730403260715561
Sticker, posted without a caption
custom 524496920953176001717custom 524273036763440587315custom 505997229793948593013custom 524269008513613593011custom 59023053728398760851
Showing the 12 most recent of 14 posts we hold for @iiNayt. 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.
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.
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.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“ضِـيَـاء” (@iiNayt), 64 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/iiNayt.
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.