Telegram RegisterThe public register of Telegram
Telegram profile photo for نمونه تست های پرورشی اختصاصی و عمومی (استاد علی اکبر)

Channel

نمونه تست های پرورشی اختصاصی و عمومی (استاد علی اکبر)

@ostad_Ali_Akbar

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

167subscribers

-2 since we began measuring on 12 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002137218435
TypeChannel
Username@ostad_Ali_Akbar
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live15 November 2026
Measurements held4
Confirmed unchanged3 times, most recently 15 November 2026
On Telegramt.me/ostad_Ali_Akbar

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 23 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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 (2 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ostad_Ali_Akbar/185 · this entry13 Jun 2025, 19:46 UTC@revayat_se/29613 Jun 2025, 19:46 UTC1.00under a minute
@ostad_Ali_Akbar/193 · this entry14 Jun 2025, 08:07 UTC@revayat_se/30414 Jun 2025, 08:07 UTC1.00under a minute
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
ChannelMatching postsText overlapTypical gapPublished first
@revayat_se12 (8/8 hand-verifiable sample passed)1.00under a minute@revayat_se (8–4)

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 4 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 13 comparable posts for this entry, running 13 June 2025 to 17 June 2025. 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @revayat_se. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

16716916812 September 2026 — 169 subscribers13 September 2026 — 169 subscribers23 October 2026 — 168 subscribers30 October 2026 — 167 subscribers12 September 202630 October 2026
4 measurements spanning 48 days, net -2. 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 167–169 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Oct 2026, 17:59167-1
23 Oct 2026, 11:10168-1
13 Sept 2026, 00:22169no change
12 Sept 2026, 23:47169first reading

Engagement

20 posts held, back to 13 June 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 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 20 posts for this entry, the most recent from 1 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 25s
Average length
33s

Measured directly from 8 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👍150.0%

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 2 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 2 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 13 June 2025 to 1 November 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

1 Nov 2025, 07:07 UTC24 viewsread 13 September 2026
Forwarded from @akhbar_KhozestanVideo

♦️رنگ‌هایی که آرامش می‌بخشند @akhbar_khozestan

17 Jun 2025, 08:35 UTC68 viewsread 13 September 2026
Forwarded from @revayat_seVideo

واتساپ، اینستاو ابزارهای هوش مصنوعی رو به این دلیل لااقل در دوران جنگ حذف کنید

17 Jun 2025, 02:03 UTC63 viewsread 13 September 2026
Forwarded from @akhbareforiVideo

گزارش‌ها از اصابت موشک به حیفا 🎥 شبکه «المیادین» گزارش داد که برخی از موشک‌های شلیک‌شده توسط ایران، به شهر بندری «حیفا» اصابت کرده‌اند. @AkhbareFori

16 Jun 2025, 12:08 UTC63 views1 reactionsread 13 September 2026

بعضی از دوستان میبینم میگن که از این فیلما چیزی در نمیاد و اگه اسرائیل برای ردیابی پدافند از فیلمای ارسالی مردم استفاده کنن احمقن و فلان ... مشخصه این حرف رو یک نفر زده که سررشته‌ای توی کامپیوتر نداره، پس توضیح میدم برای دوستانی که نمیدونن! هر فایلی که توی کامپیوتر هست همراهش کلی MetaData یا فراداده هست که هرکار کنید باهاش میره. با روش‌های معمول اصلا نمیشه حذفشون کرد! یه نمونه، دادگاه جانی‌دپ و امبرهرد بود که امبر…

👍1

16 Jun 2025, 11:02 UTC≈2,380 views1 reactionsread 13 September 2026

چرا نباید از لحظات حمله دشمن و حملات موشکی خودمون فیلم بگیریم و منتشر کنیم؟؟ اولا باعث میشه دشمن بفهمه که اون حمله ای که کرده موفق بوده یا نه: ۱- اگر موفق بوده که روحیه دشمن بالا میره و همین کلیپ رو به شدت با رسانه هاش پخش میکنه و سبب تضعیف روحیه مردم ما و افزایش هرج و مرج میشه. ۲-اگر موفق بوده باشه دیگه دشمن نیاز نیست تلاش دوباره برای زدن اونجا بکنه و این یعنی صرفه جویی در وقت، تسلیحات و کاهش ریسک دشمن. ۳-اگر ناموف…

❤1

16 Jun 2025, 05:21 UTC52 viewsread 13 September 2026
Forwarded from @revayat_sePhoto

آقای دایی سه روز از جنگ گذشته، کجایی؟نکنه اینترنت نداری

15 Jun 2025, 14:54 UTC50 viewsread 13 September 2026

🔴سردار رادان فرمانده فراجا: اگر خانه‌تان را به‌تازگی به شرکتی اجاره داده‌اید فوراً به پلیس اعلام کنید‌.

14 Jun 2025, 19:26 UTC52 viewsread 13 September 2026
Video

ویرانی گسترده ناشی از موشکی که در منطقه مرکزی اسراییل سقوط کرد. عکسی که توسط یکی از ساکنان محلی در شبکه‌های اجتماعی منتشر شده است پروکسی | پروکسی | پروکسی | پروکسی |

14 Jun 2025, 10:33 UTC54 viewsread 13 September 2026
Forwarded from @revayat_seVideo

ماشالله به ایران قوی😍

14 Jun 2025, 08:07 UTC46 viewsread 13 September 2026

بنظر من تو این مملکت خفن ترین باهوش ترین فرد رهبر جمهوری اسلامی دوبار پیشبینی کرد بامذاکره چه بلایی سرمون میاد اما گوش ندادیم!

14 Jun 2025, 06:47 UTC48 viewsread 13 September 2026

مردم شریف ایران اگه ماشینی مثل کامیون،نیسان یا هر ماشین مشکوکی دیدین سریعا با ۱۱۳ (وزارت اطلاعات) تماس بگیرید و اطلاع بدید،چون پشت این ماشین ها پهپاد دیده شده.

Showing the 12 most recent of 20 posts we hold for @ostad_Ali_Akbar. 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

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

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.

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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“نمونه تست های پرورشی اختصاصی و عمومی (استاد علی اکبر)” (@ostad_Ali_Akbar), 167 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/ostad_Ali_Akbar.

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.