1395/03/14
کتاب ؛
باید تبری باشد بر دریای یخ بسته درون ما 📚
.
.
.
شعر 👈 @Iove_Poems
.
سخن بزرگان 👈 @ZhawChannel
.
تیکهکتاب و عکسنوشته 👈 @Official_Hich
.
Created
3 June 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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 why it has no browse page of its own yet.
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 word for word on 2 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 (5 of the pairs behind the counts below)
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. 1 of the 1 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 29 comparable posts for this entry, running 30 July 2026 to 8 August 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).
Across the whole group of 3, the earliest publisher we hold is @StooryText. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 8 August 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.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
17 measurements spanning 16 days, net -253. 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 35,608–35,937 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 03:54
35,646
-17
20 Aug 2026, 19:48
35,663
-11
19 Aug 2026, 19:37
35,674
-16
18 Aug 2026, 16:04
35,690
-24
17 Aug 2026, 16:28
35,714
-19
16 Aug 2026, 09:06
35,733
-15
14 Aug 2026, 21:46
35,748
-26
13 Aug 2026, 11:18
35,774
-12
12 Aug 2026, 09:03
35,786
-21
11 Aug 2026, 11:14
35,807
-16
10 Aug 2026, 08:13
35,823
-15
9 Aug 2026, 05:03
35,838
-12
8 Aug 2026, 06:37
35,850
-25
7 Aug 2026, 09:36
35,875
-16
6 Aug 2026, 06:17
35,891
-8
6 Aug 2026, 01:50
35,899
no change
5 Aug 2026, 23:42
35,899
first reading
Engagement
210 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 36 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
0.946%
avg views ÷ 35,646 subscribers
Avg views / post
337
210 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
210
of 210 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 22 August 2026
Posts held
210 (27 July 2026 – 22 August 2026)
Views total
70,792
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 16:36 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
≈10,100
Videos
≈1,610
Links
≈2,510
Lifetime counters from Telegram’s own channel header, read 22 August 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
11m 14s
Average length
42s
Measured directly from 16 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.
آغاز امامت منجی عالم بشریت حضرت مهدی عجل الله تعالی فرجه الشریف بر منتظران دولت یار تبریک و تهنیت باد 💐💐💖💖
اللّٰهُمَّعَجِّلْلِوَلِیِّکَالْفَرَجَبِحَقِّزَیْنَبَالْکُبری
.
ارتعاش اسم خیلی مبحث مهمیه
هرکدوم از حروف الفبا داری ارتعاش و فرکانس هست
اسم ماهم مجموعی از حروف هستش که ارتعاش خاص خودش رو داره
که این ارتعاش هارو به جهان هستی میفرستیم🌍🧠
بیا اینجا ارتعاش اسمت رو محاسبه کن:
@esm
آجَرَكَ اللهُ یَا مَوْلَانَا یَا بَقِيَّةَ اللّه
🏴 شهادت مظلومانهی یازدهمین اختر تابناک امامت و ولایت، حضرت امام حسن عسکری علیهالسلام را به محضر مبارک حضرت ولیعصر عجلاللّهتعالیفرجهالشریف و عموم شیعیان و ارادتمندان اهلبیت علیهمالسلام تسلیت عرض می نمائیم.
🌷 صلوات امام عسکری علیهالسلام که آموزه و هدیه ای از جانب شخص مبارک خودشان است :
اللّٰهُمَّ صَلِّ عَلَى الْحَسَنِ بْنِ عَلِيِّ بْنِ مُحَمَّدٍ الْبَرِّ الت…
ارتعاش اسم خیلی مبحث مهمیه
هرکدوم از حروف الفبا داری ارتعاش و فرکانس هست
اسم ماهم مجموعی از حروف هستش که ارتعاش خاص خودش رو داره
که این ارتعاش هارو به جهان هستی میفرستیم🌍🧠
بیا اینجا ارتعاش اسمت رو محاسبه کن:
@esm
🔞🔞🔞🔞🔞🔞
افراد کم سن و سال به هیچ عنوان کلیک نکنند
👇👇
https://t.me/+fmu-8Gn1I3k3MTc0
https://t.me/+fmu-8Gn1I3k3MTc0
ورود افراد 18_ ممنوع⛔️(بی پرده)
Showing the 12 most recent of 210 posts we hold for @BooK_Readiing. 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 — 1,098,095 of 1,583,249entries 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 3 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
3
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
3
vacant every time we have ever looked
@BooK_Readiing named 3 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.
@razeservat named in 4 posts, 8 August 2026 – 16 August 2026
@karrr named in 3 posts, 8 August 2026 – 18 August 2026
@daramd named in 2 posts, 8 August 2026 – 18 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Amir! @AmirHossein_injast · 89,065 Telegram ranks this channel #75 of 87 here — alongside 86 others — read 17 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“BOOK™” (@BooK_Readiing), 35,646 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BooK_Readiing.
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.
