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 11 August 2026 and assigned it the closest of 31 fixed categories, at 67% 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 (1 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. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 12 April 2025 to 5 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 @agriweath. 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.
14 measurements spanning 42 days, net -80. 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 3,547–3,651 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Sept 2026, 18:21
3,559
-5
14 Sept 2026, 12:59
3,564
-10
11 Sept 2026, 03:36
3,574
-4
6 Sept 2026, 15:59
3,578
-3
2 Sept 2026, 05:34
3,581
-7
30 Aug 2026, 02:37
3,588
-8
27 Aug 2026, 09:16
3,596
-9
23 Aug 2026, 23:57
3,605
-2
20 Aug 2026, 14:43
3,607
-11
17 Aug 2026, 19:58
3,618
-10
15 Aug 2026, 03:16
3,628
-1
11 Aug 2026, 17:31
3,629
-10
7 Aug 2026, 12:33
3,639
no change
7 Aug 2026, 12:22
3,639
first reading
Engagement
20 posts held, back to 12 April 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
4m 54s
Average length
4m 54s
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
170 reactions across 16 posts, in 6 distinct kinds. The most used accounts for 54.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
92
54.1%
👍
64
37.6%
😢
9
5.29%
👎
2
1.18%
🙏
2
1.18%
😁
1
0.588%
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 18 of the 20 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 170 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 April 2025 to 5 August 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.
⚠️ خطری که همیشه دیده نمیشود...
🌿 برخی پزشکان و پژوهشگران هشدار میدهند که تماس مداوم با سموم کشاورزی و ورود زودهنگام به باغ و مزرعه پس از سمپاشی، میتواند سلامت کشاورزان و کارگران را با خطرات جدی روبهرو کند.
😷 استفاده از تجهیزات ایمنی، رعایت فاصله مناسب پس از سمپاشی و مصرف سموم استاندارد، از مهمترین راههای کاهش این خطرات است.
🌱 سلامت کشاورز، اولین قدم برای تولید محصول سالم است.
لینک دسترسی به اپ
دانلود اپلیکی…
قرار بود آبیاری را مثل همیشه، ساعت ۶ عصر شروع کنند.
همهچیز آماده بود؛ کارگرها کنار باغ منتظر بودند و فقط باید شیر آبیاری باز میشد.
اما قبل از شروع، کشاورز نگاهی به اطلاعات شبکه هواشناسی آباد انداخت.
دادههای محلی نشان میداد شرایط باغ، با پیشبینی عمومی منطقه یکسان نیست. همین چند درجه اختلاف، کافی بود تا تصمیمش را عوض کند و زمان آبیاری را تغییر دهد.
گاهی تفاوت میان یک تصمیم معمولی و یک تصمیم درست، فقط چند کیلومتر …
🌱 هر باغ، نیاز تغذیهای متفاوتی دارد.
هوش مصنوعی آباد با بررسی اطلاعات باغ شما، برنامه تغذیه اختصاصی پیشنهاد میدهد؛ از انتخاب کود مناسب تا روش مصرف و تشخیص مشکلات تغذیهای گیاه.
🔗 ۵ گجت هوشمند تغذیه آباد را ببینید:
ورود به صفحه گجتهای برنامه تغذیه
----------------------------------------------------------
لینک دسترسی به اپ
دانلود اپلیکیشن از بازار
❇️@agriweath
💚 اگر دوست دارید از تولید آموزشهای رایگان کشاورزی آباد حمایت کنید، یک دقیقه وقت بگذارید.
این ویدئو را در آپارات هم ببینید و اگر مطالب برایتان کاربردی بود، کانال کشاورزی آباد را دنبال کنید. همین حمایتهای کوچک، به ادامه تولید محتوای آموزشی باکیفیت کمک بزرگی میکند.
🎥 لینک ویدئو:
https://www.aparat.com/v/saiypq7
----------------------------------------------------------
لینک دسترسی به اپ
دانلود اپلیکیشن از بازار
❇️…
🌿 نمیدانید گجت «نیاز کودی فعلی» دقیقاً چه اطلاعاتی به شما میدهد و چطور باید ازش استفاده کنید؟
در این ویدئوی کوتاه، مرحلهبهمرحله نحوه استفاده از این گجت را آموزش دادهایم تا بتوانید از اطلاعات آن برای تصمیمگیری بهتر در کوددهی استفاده کنید.
🎥 ویدئو را ببینید و اگر برایتان مفید بود، آن را با سایر کشاورزان هم به اشتراک بگذارید.
لینک دسترسی به اپ
دانلود اپلیکیشن از بازار
❇️@agriweath
اگر هشدار گرما یک روز زودتر به دستت برسد، چه کاری انجام میدهی؟
همین یک روز میتواند تفاوت بین یک باغ سالم و یک خسارت سنگین باشد.
سرویس هشدار گرمازدگی آباد قبل از رسیدن موج گرما، شما را باخبر میکند و برای روزهای پرخطر، اقدامات پیشنهادی در اختیارتان قرار میدهد.
اما این سرویس دقیقاً چطور کار میکند؟ چه اطلاعاتی نمایش میدهد؟ و هشدارها بر چه اساسی صادر میشوند؟
همه جزئیات را در صفحه معرفی ببینید:
🔗 🔗 ورود به صف…
🌿 یک تصمیم، گاهی از چندین نوبت سمپاشی ارزشمندتر است.
آقای احمدی بعد از مشاهده آفت در باغش، تصمیم داشت همان روز سمپاشی کند. اما قبل از شروع، گجت «سمپاشی در گلدهی و میوهدهی» در اپلیکیشن آباد را امتحان کرد.
بعد از وارد کردن اطلاعات باغ، توصیهای اختصاصی دریافت کرد که نشان میداد سمپاشی در این مرحله میتواند به گلها آسیب بزند و روی عملکرد نهایی محصول اثر بگذارد.
او زمان سمپاشی را اصلاح کرد و تصمیمش را بر اساس شرایط …
.
#شپشک_آرد_آلود (قسمت 1 از 2)
🍀 این آفت در باغ، شیبهای متمایل به سمت آفتابی شمالی را ترجیح میدهد؛
🍀 در مناطق گرم و معتدل در مقایسه با مناطق سرد، شرایط مناسبتری جهت ایجاد تراکم بالاتر و فعالیت بیشتر آفت فراهم است؛
🍀 در باغاتی که تراکم زیادی دارند، شرایط فعالیت آفت مناسبتر بوده و لذا شرایط برای طغیانی شدن آفت فراهم میباشد؛
🍀 بین این آفت و مورچهها نوعی همزیستی وجود دارد به نحوی که مورچه از عسلک تولید شده توسط…
🌾 کشاورز عزیز!
میدونی اشعهی UV در بعضی روزها و ساعات میتونه به شدت به پوست و چشمها آسیب بزنه و حتی به محصولاتت هم ضرر بزنه؟
با آباد:
🔸هر هفته هشدارهای دقیق UV رو دریافت کن!
🔸️ ما بهت میگیم چه روزها و چه بازههایی از روز UV بالاست
🔸️ و چه اقداماتی باید انجام بدی تا با خیال راحت کار کنی!
💡 حفاظت از سلامتی و محصولاتت فقط با آباد!
🎯 همین حالا آباد رو نصب کن و رایگان استفاده کن!
👇👇👇👇👇👇👇👇👇👇👇
دانلود مستقیم آباد
.
#بیماری_شانکر_سیتوسپورایی (فیتیله نارنجی) (قسمت 2 از 2)
⏰ مدیریت بیماری:
1️⃣ هر عاملی که باعث تقویت درخت شود مانند کود، آب کافی، خاک با عمق مناسب و جلوگیری از زخمی و شکسته شده شاخهها و صدمه حشرات پوست خوار احتمال ایجاد عفونت و در نتیجه خسارت بیماری را کاهش میدهد؛
2️⃣ هرس و سوزاندن شاخههای خشک و نیمه خشک؛
3️⃣ ضدعفونی محل بریدگی شاخههای هرس شده با محلول بردو 2 درصد؛
4️⃣ پانسمان محل خروج فیتیلهها با ترکیبات …
.
#بیماری_شانکر_سیتوسپورایی (فیتیله نارنجی) (قسمت 1 از 2)
🌳 شاخههای مبتلا به بیماری به سهولت از شاخههای سالم قابل تشخیص میباشد، زیرا برگهای آن شاخه، پژمرده و سبزخشک میشود و متعاقبا فیتیلههای نارنجی، زرد یا قهوهای عامل بیماری که در واقع اسپورهای قارچ است در سطح شاخهها ظاهر میگردد؛
🌳 علائم بیماری فتیله نارنجی شامل زرد شدن و رسیدگی زودرس میوهها، کاهش رشد شاخهها و رگزدایی برگها است؛
🌳 این بیماری معمولاً د…
❤13
Showing the 12 most recent of 20 posts we hold for @nabaatAI. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
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.
🌾کانال کشاورزان و دامداران کشور @keshavarzan_dam · 85,473 Telegram ranks this channel #1 of 73 here — alongside 72 others — read 18 August 2026
هواشناسی ایران🔖 @iran_met · 46,284 Telegram ranks this channel #57 of 70 here — alongside 69 others — read 27 August 2026
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.
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 18 September 2026 — this
entry's latest reading, not the date you are reading this.
“دستیار هوشمند کشاورزی نبات” (@nabaatAI), 3,559 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nabaatAI.
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.
