Personal blog — 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 80% 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 1 other registered channel. 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)
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. 5 of the 16 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 19 comparable posts for this entry, running 2 August 2026 to 7 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 2, the earliest publisher we hold is @drmojtaba_shakoori. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 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 1 other registered channel, 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.
35 measurements spanning 52 days, net -550. 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 25,753–26,468 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
27 Sept 2026, 17:55
25,835
-73
17 Sept 2026, 20:22
25,908
-33
15 Sept 2026, 18:59
25,941
-16
14 Sept 2026, 05:20
25,957
-17
12 Sept 2026, 16:19
25,974
-32
10 Sept 2026, 18:57
26,006
-50
7 Sept 2026, 18:41
26,056
-42
4 Sept 2026, 19:41
26,098
-17
3 Sept 2026, 06:26
26,115
-8
2 Sept 2026, 02:38
26,123
-21
1 Sept 2026, 02:15
26,144
-13
30 Aug 2026, 23:38
26,157
-4
30 Aug 2026, 01:41
26,161
-3
29 Aug 2026, 01:07
26,164
-9
28 Aug 2026, 02:07
26,173
-15
26 Aug 2026, 23:54
26,188
-15
25 Aug 2026, 20:23
26,203
-8
24 Aug 2026, 19:15
26,211
-13
23 Aug 2026, 02:24
26,224
-13
21 Aug 2026, 13:03
26,237
first reading
Engagement
198 posts held, back to 2 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 75 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.99%
avg views ÷ 25,835 subscribers
Avg views / post
2,060
69 posts measured
Reaction rate
5.38%
reactions ÷ views · ER floor
Posts in window
69
of 198 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 30 September 2026
Posts held
198 (2 August 2026 – 30 September 2026)
Views total
142,377
Reactions total
7,658
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
30 Sept 2026, 17:06 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
≈30
Videos
≈50
Links
≈1,540
Lifetime counters from Telegram’s own channel header, read 30 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
14s
Average length
14s
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
24,501 reactions across 198 posts, in 8 distinct kinds. The most used accounts for 35.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
8,770
35.8%
👍
6,935
28.3%
👌
3,524
14.4%
👏
2,987
12.2%
💔
1,188
4.85%
😭
713
2.91%
🙏
271
1.11%
🤔
113
0.461%
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 198 of the 198 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 24,501 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 198 most recent posts we hold, published 2 August 2026 to 30 September 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.
ازدواج با عشق شروع میشه، ولی با مهارت زنده میمونه. ❤️
اینا ۱۰ قانونیه که تحقیقات نشون میده میتونن رابطه رو از فرسودگی نجات بدن.
۱. جلوی کسی با هم بحث نکنید، مخصوصاً جلوی خانوادههاتون.
چون رابطهتون حریم داره؛ وقتی دعوا رو میبرید بیرون، رابطه حس امنیتش رو از دست میده.
۲. با دلچرکینی نخوابید. 🌙
واقعاً شب، احساسات حلنشده رو بزرگتر میکنه. حتی یه گفتوگوی کوتاه آخر شب، رابطه رو از سقوط نجات میده.
۳. وقتی دلخورید، …
یادآوری امروزت:
هرچه انسان از درون غنیتر باشد، آرامتر و کمادعاتر است؛
هرچه درونش تهیتر باشد، بیرونش پر از صدا و نمایش میشود.
عمق، نیازی به اعلام ندارد...
متأهل عزیز...
موبایلت رو بذار کنار و بهجای اکسپلورگردی، برو کنار همسرت بشین و ببین چی میگه، باهاش صحبت کن.
ازش بپرس روزش چطور گذشت؟ به چیزی نیاز نداره؟ این روزها حالش چطوره؟
بپرس مسئله یا مشکلی هست که بهت نگفته باشه و از چیزی ناراحت باشه؟
نگران نباش... اون گوشی همیشه هست.
یادآوری امروزت:
هر انسانی داستانی دارد...
داستانی که اگر واقعاً بشنوی، شاید اشکهایت جاری شود.
آن مردی که در ترافیک بیحوصلگی میکند، شاید شب قبل را کنار تخت بیمار عزیزش گریه کرده...
آن زنی که با خشونت پاسخ میدهد، شاید سالهاست صدایش را کسی نشنیده...
همهی ما بارها قضاوت کردهایم، بیآنکه بدانیم پشت هر نگاهی، دنیایی از رنجها و آرزوها پنهان است.
زندگی هر کسی کتابی است که ما فقط یک صفحه از آن را خواندهایم. شاید …
📙 یه سؤال: آخرین رمانی که واقعاً نتونستی زمین بذاری چی بود؟
اگه مدتهاست دنبال یه داستان تازهای که دوباره غرقش بشی، به کتابباف سر بزن.
📖 هر شب یک رمان تازه
🎧 هم pdf داریم، هم کتاب صوتی
📮 هر ماه درخواست رایگان کتاب
همین الان عضو کتابباف شو که گممون نکنی👇👇👇
https://t.me/+BFb8ZGIxF9lkMWZk
نوشته بود:
من و همسرم یه عادت باحال پیدا کردیم؛
اگه یکیمون یه روز بدی داشته باشیم، اون یکی میپرسه:
میخوای دلداری بدم یا راهحل؟!
همین یه جمله جلوی ۹ تا از ۱۰ دعوا رو میگیره.
تا حالا دقت کردی وقتی یه مسیر رو اشتباه میری، گوگل مپ سرت داد نمیزنه؟
نمیگه «چقدر خنگی!» یا «گند زدی!»… فقط خیلی آروم میگه: «در حال پیدا کردن مسیر جدید…» و یه راه جدید بهت نشون میده.
کاش ما هم با خودمون همینجوری بودیم. وقتی یه تصمیم اشتباه میگیریم یا یه راه رو غلط میریم، به جای اینکه خودمون رو سرزنش کنیم، فقط آروم به خودمون بگیم:
«خب، مسیر جدید رو پیدا میکنیم.» شاید اون پیچ اشتباه شروع یه جادهی قشنگتر و پرماج…
چیزایی که میخوام دوست صمیمیم بدونه:
من عاشق اینم که وقتی کنارتم،
میتونم خودِ واقعیم باشم.
لازم نیست نقش بازی کنم، خودم رو بهتر از چیزی که هستم نشون بدم یا نگران قضاوتت باشم.
اشکالی نداره اگه فوراً جواب پیامم رو ندی،
یا بعضی وقتا حوصلهی بیرون رفتن نداشته باشی.
میدونم تو هم زندگی و دغدغههای خودت رو داری و قرار نیست همیشه در دسترس باشی.
هیچوقت لازم نیست کنارم وانمود کنی که حالت خوبه.
قرار نیست همیشه بخندی یا قو…
❤45👌8👏4
Showing the 12 most recent of 198 posts we hold for @ardeshire_rostami. 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.
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 5 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
محمد صالح علا @mohammad_salehala1 · 1,031 (as read 13 September 2026)#58
Read from Telegram’s recommendation API, most recently 13 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
کتابخانه @booksofus · 53,405 Telegram ranks this channel #71 of 84 here — alongside 83 others — read 23 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 27 September 2026 — this
entry's latest reading, not the date you are reading this.
“پادکستهای اردشیر رستمی” (@ardeshire_rostami), 25,835 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/ardeshire_rostami.
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.
