Channel
@BE_WAGHTE_KETAB
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
535subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001684774734 |
|---|---|
| Type | Channel |
| Username | @BE_WAGHTE_KETAB |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/BE_WAGHTE_KETAB |
Literature — 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 11 August 2026 and assigned it the closest of 31 fixed categories, at 81% 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.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @BE_WAGHTE_KETAB/21807 · this entry6 Aug 2026, 06:18 UTC | @SHENAKHT12/1116016 Aug 2026, 06:19 UTC | 0.98 | under a minute |
| @SHENAKHT12/1115916 Aug 2026, 04:40 UTC | @BE_WAGHTE_KETAB/21801 · this entry6 Aug 2026, 04:42 UTC | 0.97 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @SHENAKHT12 | 9 (8/8 hand-verifiable sample passed) | 0.98 | 57 minutes | this entry (6–3) |
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. 3 of the 3 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 6 August 2026 to 6 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.
Across the whole group of 2, the earliest publisher we hold is @BE_WAGHTE_KETAB — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 12:37 | 535 | +2 |
| 4 Sept 2026, 02:41 | 533 | -2 |
| 28 Aug 2026, 02:43 | 535 | -2 |
| 20 Aug 2026, 06:18 | 537 | +2 |
| 13 Aug 2026, 07:24 | 535 | -6 |
| 6 Aug 2026, 18:18 | 541 | no change |
| 6 Aug 2026, 09:38 | 541 | first reading |
19 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
@BE_WAGHTE_KETAB 📹 روایت خبرنگار اینترنشنال در اسرائیل از درماندگی صهیونیستها: 🔅دیوانه شدیم!. مردم اسرائیل خسته شده اند؛ ایران زندگی روزمره اسرائیلی ها را مختل کرده؛ مردم نمی توانند تصمیمات درستی بگیرند!.ارتش اسرائیل فرسوده شده است!/ایران ما @BE_WAGHTE_KETAB
@BE_WAGHTE_KETAB 📖معرفی کتاب"جمهوری خلق نسیان؛لوئیزا لیم؛ترجمه مسعود یوسف حصیرچین" 👈ایده حذف،بازنویسی ومخدوش کردن تاریخ،ازهمان جمله نخنما ومستعمل "تاریخ را فاتحان می نویسند" از دیرباز وجود داشته است.درخصوص بسیاری از وقایع تاریخی درگذشته شک وشبهههای بسیاری وجود دارد کـه برطرف شدنی هم نیستند چون هیچ سند مکتوبی جز آن چه برندگان نوشته اند وجود ندارد و این خود نشانیست بر تناقض ابدی تاریخ در روایت حقیقت. 🔅در سده…
@BE_WAGHTE_KETAB 🌓خرازی بعد از دروغهای تکذیبشده؛ این بار نسخه سرنگونی دولت را پیچید / وقتی رویای قدرت جای قانون را میگیرد 👈به گزارش تابناک،محمدباقرخرازی در تازهترین اظهارات خود مدعی شده است که "۴۰ سال" با آیت الله سید مجتبی خامنهای رابطه نزدیک و جلسات خصوصی داشته، همه پیش بینی هایش درست از آب درآمـده و حتی دولت پزشکیان "سـال چـهارم را نخواهد دید". 🔅همین فرد چند روز قبل نیز ادعاهایی را به رهبر انقلاب …
@BE_WAGHTE_KETAB 📹 مذاکرات ایران و آمریکا؛ چند قدم جلو، چند قدم عقب 📣ونس، معاون ترامپ درخصوص روند مذاکرات با ایران گفت: 🔅مذاکره با ایران مانند قدم به جلو وعقب است؛ ایرانیها بسیار سرسخت هستند /تلویزیون اقتصاد آنلاین @BE_WAGHTE_KETAB
@BE_WAGHTE_KETAB 📹 به مناسبت سالروز حمله اتمی آمریکا به هیروشیما 🕰ساعت ۸:۱۵صبح روز۶ آگوست۱۹۴۵ ومردمی که زندهزنده درآتش انفجار سوختند! 🎬 ۱): مردمی که زنده زنده در آتش انفجار سوختند 🔅 روایت عینی یکی از بازماندگان از حمله اتمی هیروشیما 🎬 ۲): شهری که خاکستر شد! 🔅صبح ۶ آگوست۱۹۴۵ جهان برای همیشه تغییرکرد و اولین بمب اتمی جهان توسط آمریکا بر سر شهر ژاپنی هیروشیما انداخته شد. 🔅 شدت انفجار برابر با انفجار پانز…
@BE_WAGHTE_KETAB ✍️استیو هانکه، استاد دانشگاه و اقتصاددان مشهور آمریکایی: 🔅تاسال ۲۰۳۰، در نهایت ممکن است روزانه تا ۱۵میلیون بشکه نفت خام از طریق خطوط لوله جدید و توسعهیافته، بدون عبور از تنگه هرمز صادر شود. 🔅امـا با این حال، هم چنان حـدود ۱۰ میلیون بشکه نفـت خام در روز هیچ مسیر جایگزینی برای صادرات نخواهد داشت. 🔅این فقط بخشی ازخسارتهاییست که جنگ ترامپ علیه ایران ایجاد کرده/برهوت تی وی @BE_WAGHTE_KETAB
@BE_WAGHTE_KETAB 📹شکست مفتضحانه دکترین تهدید و تنش ترامپ 📣"عبدالباری عطوان" نویسنده و تحلیلگر سیاسی: 🔅الان واقعیتی درمیدان وجود دارد:ایران است که بر تنگه هرمزمسلط است وهیچ نفتکشی جـرئت ندارد بدون اجـازه او عبور کند اگـر بگویند تنگه هرمز را بستیم تمام شد بسته خواهد شد. 🔅ترامپ درجنگی گرفتار شده که نمیداند چطور از آن خارج شود.اوضاع اصلا آنطور که آنهامیخواهند.پیش نمیرود،جنگی بدون هدف،جنگی که هیچ طرحی بر…
@BE_WAGHTE_KETAB 📹از اصلاحات میجی تا ویرانی هیروشیما | داستان توسعه ژاپن 📣گوینده: احمد هاشمی: 🔅"این است فریاد ما، این است آرزوی ما، صلح در تمام دنیا" 🔅اگه سری به عکس های یادبود پسربچه ای به نام ساداکو ساساکی در پارک صلح شهر هیروشیما بزنید این عبارت رو میبینید. جایی که تندیس یه پسربچه ژاپنی با یه درنای طلایی تو دستش به شما لبخند میزنه. 🔅"داستان درنا های کاغذ" که هر ساله در سالگرد بمـباران هیروشیـم…
@BE_WAGHTE_KETAB ✍️ علی حسینی نماینده ادوار ۵ و ۶ مجلس در کانال تلگرامی خود نوشت: 🔅آمریکا در سال ۱۹۹۹ اساسنامه رم(دادگاه بینالمللی لاهه) را امضا کرد،اما هرگزآن راتصویب نکرد. 🔅بایدآمریکاراشناخت.گذشته آمریکاچراغی پرنور برای آینده ماست و ربطی باجنایات داخلی حکومت نداردو نفی آن نیست. 🔅 کشتار وحشتناک سرخپوستان بومی وصاحبان اصلی سرزمین آمریکا 🔅کشتاروحشیانه قریب به یک میلیون نفردر فیلیپین وآوردن قحطی وفقر وبیم…
@BE_WAGHTE_KETAB 📹نخستین و واپسین دیدار 🔆روایتی شنیدنی از دکتر عبدالکریم سروش درباره مهندس مهدی بازرگان 🔅دکتر عبدالکریم سـروش در این ویدیو، از نخستین آشنایی و آخرین دیدار خود با مهندس مهدی بازرگان روایت میکند؛ 🔅خاطرهای خواندنی و تأملبرانگیز که گوشهای از شخصیت و منش این اندیشمند و سیاستورز برجسته را به تصویر میکشد./بنیاد فرهنگی مهندس مهدی بازرگان @BE_WAGHTE_KETAB
@BE_WAGHTE_KETAB ✍️اکبر اعلمی در کانال تلگرامی خود نوشت: 🔅محمدباقر خرازی، دبیرکل حزب الله ایران و برادر عروس رهبر شهید ج.ا.ایران، در واکنش به تکذیبیه دفتر آقای سید مجتبی خامنهای، در فضای مجـازی نوشت:"گرچه به احترام قائد شهید و نیز رهبر معظم حاضر، تکذیبیه روابط عمومی و دفتر نشر آثار را حدوثاً میپذیریم،ولی امیدواریم پس از تغییرات مهم آینده درحوزه دفاتر فوق، این تکذیبیه همچنان باقی بماند. خداوند ما را در …
@BE_WAGHTE_KETAB 🌓غریبآبادی: پیامهایی از آمریکا دریافت کردهایم مبنی بر آمادگی برای بازگشت به تعهدات 🔅غریب آبادی گفته در روز های اخیر هیـچ مذاکره مستقیمی با آمریکا انجام نشده. همچنین خبر دعوت وزیر خارجه و رئیس مجلس به پاکستان درسته، اما هنوز برنامه نهایی برای این سفر قطعی نشده. 🔅غریبآبادی تأکید کرده توی این مدت، مسیر رایزنیها از طریق عمان بوده و فعلاً خبری ازمذاکره مستقیم با آمریکا نیست.درباره ورود به مرح…
Showing the 12 most recent of 19 posts we hold for @BE_WAGHTE_KETAB. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“به وقت کتاب (داود بهرامی سیاوشانی)” (@BE_WAGHTE_KETAB), 535 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/BE_WAGHTE_KETAB.
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.