These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Views per post sit far below this size band
5.5 average views per post against 49,778 subscribers — an engagement rate of 0.011%. Across the 2,113 registered channels in the same cohort — 31,628–99,881 subscribers, posting mainly in Arabic — the middle half sit between 1.56% and 11.4%, with a median of 4.98%.
What this was computed from
Window
30 days (4 August 2026 – 3 September 2026)
Posts measured
1,122 of 1,122 published in the window (1,122 exact, 0 rounded by Telegram)
Views totalled
6,185
Mature posts only
0.627% over 10 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_low, last confirmed 3 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Growth
27 measurements spanning 27 days, net -1,684. 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 49,525–51,715 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
3 Sept 2026, 06:08
49,778
-69
1 Sept 2026, 22:24
49,847
-37
31 Aug 2026, 23:18
49,884
-87
30 Aug 2026, 23:25
49,971
-44
30 Aug 2026, 00:19
50,015
-51
29 Aug 2026, 01:28
50,066
-49
28 Aug 2026, 03:44
50,115
-58
27 Aug 2026, 01:47
50,173
-65
26 Aug 2026, 00:43
50,238
-47
25 Aug 2026, 03:24
50,285
-78
23 Aug 2026, 23:17
50,363
-108
22 Aug 2026, 10:06
50,471
-86
20 Aug 2026, 20:55
50,557
-72
19 Aug 2026, 18:43
50,629
-68
18 Aug 2026, 21:45
50,697
-65
17 Aug 2026, 18:37
50,762
-66
16 Aug 2026, 16:47
50,828
-109
14 Aug 2026, 22:04
50,937
-64
13 Aug 2026, 15:56
51,001
-70
12 Aug 2026, 18:15
51,071
first reading
Engagement
1,123 posts held, back to 29 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 59 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.011%
avg views ÷ 49,778 subscribers
Avg views / post
5.5
1,122 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,122
of 1,123 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 September 2026
Posts held
1,123 (29 July 2026 – 3 September 2026)
Views total
6,185
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 18:46 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.
What this channel posts
Photos
≈1,770
Videos
≈28
Links
≈1,810
Lifetime counters from Telegram’s own channel header, read 3 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
2m 48s
Average length
28s
Measured directly from 6 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.
Showing the 12 most recent of 1,123 posts we hold for @zd_f3. 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.
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.
Handles this channel named that no longer answer
Dead references
10
handles named in this channel’s posts, vacant today
Evidenced gone
9
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@zd_f3 named 10 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@x16x0 named in 3 posts, 16 August 2026 – 20 August 2026 · confirmed gone 21 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@x95x0 named in 2 posts, 31 August 2026 – 31 August 2026 · confirmed gone 2 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@x_vcrx named in 1 post, 18 August 2026 – 18 August 2026 · confirmed gone 21 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@epxbdf0i0oo5yzky named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 30 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@absroley named in 1 post, 13 August 2026 – 13 August 2026 · confirmed gone 3 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@shitmaybetamara named in 1 post, 13 August 2026 – 13 August 2026 · confirmed gone 18 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@absrolel named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 14 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@altay557 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 8 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@yuipd6 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 13 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@ze_hx named in 16 posts, 8 August 2026 – 3 September 2026
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 3 September 2026 — this
entry's latest reading, not the date you are reading this.
“بوت♥️زخرفة♥️زخارف♥️زخرفه♥️اسماء” (@zd_f3), 49,778 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/zd_f3.
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.
