Music — 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 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.
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 4 other registered channels. 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. 35 of the 35 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 360 comparable posts for this entry, running 6 August 2026 to 10 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).
Recorded under the keys clone_copy · clone_mutual, last confirmed 11 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.
Growth
62 measurements spanning 94 days, net -3,701. 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 44,688–50,605 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)
Subscribers
Change
9 Nov 2026, 19:59
46,221
+850
8 Nov 2026, 10:46
45,371
-41
7 Nov 2026, 07:39
45,412
-50
6 Nov 2026, 07:11
45,462
-45
5 Nov 2026, 07:46
45,507
-44
4 Nov 2026, 06:36
45,551
-26
3 Nov 2026, 08:49
45,577
-42
2 Nov 2026, 12:05
45,619
-41
1 Nov 2026, 10:35
45,660
-39
31 Oct 2026, 10:11
45,699
-36
30 Oct 2026, 12:54
45,735
-40
29 Oct 2026, 13:49
45,775
-41
28 Oct 2026, 14:41
45,816
-50
27 Oct 2026, 11:28
45,866
-38
26 Oct 2026, 10:36
45,904
-53
25 Oct 2026, 08:30
45,957
-31
24 Oct 2026, 11:37
45,988
-49
23 Oct 2026, 10:46
46,037
-35
22 Oct 2026, 11:09
46,072
-47
21 Oct 2026, 06:11
46,119
first reading
Engagement
2,078 posts held, back to 6 August 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 230 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.23%
avg views ÷ 46,221 subscribers
Avg views / post
568
582 posts measured
Reaction rate
0.076%
reactions ÷ views · ER floor
Posts in window
582
of 2,078 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. It is computed over the 9 of 582 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 11 November 2026
Posts held
2,078 (6 August 2026 – 11 November 2026)
Views total
330,518
Reactions total
24
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 13:25 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
≈3,620
Videos
≈13
Links
≈25
Lifetime counters from Telegram’s own channel header, read 11 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
9s
Average length
9s
Measured directly from 1 video 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.
Reaction mix
117 reactions across 16 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5979079322005148203
117
100.0%
Custom emoji. One 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 count beside it is 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 19 of the 1,000 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 117 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 September 2026 to 11 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 Stars
Stars received
2
across the posts below
Posts paid on
2
of 1,000 we hold a reading for · 0.2%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @i_cfs. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 24 September 2026 to 11 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 2 of 582 posts held from the last 30 days (0.344%) 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).
نه تو مانی و نه اندوه؛
و نه هیچ یک از مردم این آبادی،
به حباب نگران لب یک رود قسم
و به کوتاهی آن لحظه ی شادی که گذشت؛ غصه هم خواهد رفت.
آن چنان که فقط خاطره ای خواهد ماند.
لحظه ها عریانند؛
به تن لحظه ی خود جامه ی اندوه مپوشان هرگز.
-سهراب سپهری.
@i_cfs
Showing the 12 most recent of 2,078 posts we hold for @i_cfs. 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.
Posts recorded as deleted after publishing
We recorded 44 posts on @i_cfs as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
20 August 2026
Most recent seen missing
26 October 2026
Median time before seen missing
26 hours
Seen missing in the last 30 days
7
Polls
The 6 most recent of 13 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 September 2026 to 11 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 2 registered channels — 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
29
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
29
vacant every time we have ever looked
@i_cfs named 29 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@giflokhti named in 11 posts, 13 August 2026 – 3 November 2026
@zendgi_zanashoi named in 7 posts, 19 August 2026 – 11 November 2026
@profile_khas named in 4 posts, 16 September 2026 – 3 November 2026
@remixshad named in 4 posts, 13 August 2026 – 15 October 2026
@cute_shop named in 4 posts, 18 August 2026 – 14 October 2026
@shopzanashoi named in 4 posts, 16 August 2026 – 4 October 2026
@tehme named in 3 posts, 15 August 2026 – 8 November 2026
@fooddecor named in 3 posts, 8 August 2026 – 28 October 2026
@lebasezir named in 3 posts, 9 August 2026 – 13 October 2026
@dr_sara named in 2 posts, 8 August 2026 – 9 November 2026
@musicbshgahi named in 2 posts, 11 September 2026 – 19 October 2026
@mame85 named in 2 posts, 18 August 2026 – 16 October 2026
@bootik_darno named in 2 posts, 13 August 2026 – 19 August 2026
@lovee named in 1 post, 9 November 2026 – 9 November 2026
@darno_bootik named in 1 post, 8 November 2026 – 8 November 2026
@gif_hot named in 1 post, 3 November 2026 – 3 November 2026
@vakill_bashii named in 1 post, 19 October 2026 – 19 October 2026
@daneshamoz named in 1 post, 19 October 2026 – 19 October 2026
@shixon_bootik named in 1 post, 16 October 2026 – 16 October 2026
@remixnab named in 1 post, 15 October 2026 – 15 October 2026
@sara_nashnas named in 1 post, 14 October 2026 – 14 October 2026
@aramis_perfume named in 1 post, 2 October 2026 – 2 October 2026
@anime named in 1 post, 26 September 2026 – 26 September 2026
@myvakil named in 1 post, 24 September 2026 – 24 September 2026
@subliminal named in 1 post, 14 September 2026 – 14 September 2026
@godproxy named in 1 post, 11 August 2026 – 11 August 2026
@confing named in 1 post, 10 August 2026 – 10 August 2026
@simpsons named in 1 post, 8 August 2026 – 8 August 2026
@hamomnude named in 1 post, 8 August 2026 – 8 August 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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“𝐂𝐅𝐒” (@i_cfs), 46,221 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/i_cfs.
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.
