Memes & entertainment — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
Observations
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.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 6 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 28 of the 28 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 515 comparable posts for this entry, running 6 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @zd_f3 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Views per post sit far below this size band
3.1 average views per post against 46,569 subscribers — an engagement rate of 0.007%. Across the 2,034 registered channels in the same cohort — 31,623–99,996 subscribers, posting mainly in Arabic — the middle half sit between 1.55% and 11.5%, with a median of 5.11%.
What this was computed from
Window
30 days (6 October 2026 – 5 November 2026)
Posts measured
1,152 of 1,152 published in the window (1,152 exact, 0 rounded by Telegram)
Views totalled
3,570
Mature posts only
0.252% over 11 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 keys clone_copy · clone_source · err_low, last confirmed 12 November 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.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
64 measurements spanning 95 days, net -5,146. 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 45,544–52,234 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)
Subscribers
Change
10 Nov 2026, 07:37
46,316
-60
8 Nov 2026, 21:55
46,376
-54
7 Nov 2026, 16:15
46,430
-42
6 Nov 2026, 17:38
46,472
-49
5 Nov 2026, 15:36
46,521
-48
4 Nov 2026, 12:47
46,569
-47
3 Nov 2026, 09:29
46,616
-43
2 Nov 2026, 08:08
46,659
-59
1 Nov 2026, 06:40
46,718
-44
31 Oct 2026, 09:15
46,762
-44
30 Oct 2026, 09:09
46,806
-38
29 Oct 2026, 11:11
46,844
-60
28 Oct 2026, 06:48
46,904
-50
27 Oct 2026, 09:46
46,954
-50
26 Oct 2026, 09:16
47,004
-36
25 Oct 2026, 08:27
47,040
-53
24 Oct 2026, 05:07
47,093
-49
23 Oct 2026, 04:36
47,142
-63
22 Oct 2026, 06:50
47,205
-71
21 Oct 2026, 01:19
47,276
first reading
Engagement
3,811 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 196 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
0.007%
avg views ÷ 46,316 subscribers
Avg views / post
3.3
1,171 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1,171
of 3,811 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 12 November 2026
Posts held
3,811 (29 July 2026 – 12 November 2026)
Views total
3,829
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Nov 2026, 00:51 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,820
Videos
≈28
Links
≈1,800
Lifetime counters from Telegram’s own channel header, read 12 November 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
1m 17s
Average length
26s
Measured directly from 3 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1,171 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).
Showing the 12 most recent of 3,811 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
19
handles named in this channel’s posts, vacant today
Evidenced gone
18
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@zd_f3 named 19 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 25 October 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 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@n_kg2 named in 1 post, 15 October 2026 – 15 October 2026 · confirmed gone 22 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@rrttqqwwp named in 1 post, 6 October 2026 – 6 October 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mm_1ar named in 1 post, 3 October 2026 – 3 October 2026 · confirmed gone 18 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hakutna named in 1 post, 16 September 2026 – 16 September 2026 · confirmed gone 19 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@german_yyy named in 1 post, 12 September 2026 – 12 September 2026 · confirmed gone 17 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@cchgfx named in 1 post, 12 September 2026 – 12 September 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hshshshshkso named in 1 post, 10 September 2026 – 10 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@m7n7y named in 1 post, 1 September 2026 – 1 September 2026 · confirmed gone 7 November 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 27 October 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 4 November 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 19 October 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 5 November 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 October 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 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@xcu9k named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 31 October 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 14 October 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 49 posts, 8 August 2026 – 12 November 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“بوت♥️زخرفة♥️زخارف♥️زخرفه♥️اسماء” (@zd_f3), 46,316 subscribers as measured 10 November 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.
