Channel
@sharyar_ir
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
2,983subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001146690482 |
|---|---|
| Type | Channel |
| Username | @sharyar_ir |
| Created | Between 1 May 2017 and 31 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/sharyar_ir |
Local community — 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 59% 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 |
|---|---|---|---|
| @sharyar_ir/1543 · this entry2 Jun 2026, 05:52 UTC | @taavoni_shahryar/4052 Jun 2026, 05:54 UTC | 1.00 | 72 seconds |
| @taavoni_shahryar/41123 Jun 2026, 10:15 UTC | @sharyar_ir/1551 · this entry23 Jun 2026, 10:16 UTC | 1.00 | 72 seconds |
| @taavoni_shahryar/41315 Jul 2026, 10:11 UTC | @sharyar_ir/1552 · this entry15 Jul 2026, 10:13 UTC | 1.00 | 2 minutes |
| @taavoni_shahryar/41415 Jul 2026, 10:16 UTC | @sharyar_ir/1553 · this entry15 Jul 2026, 10:17 UTC | 1.00 | 72 seconds |
| @taavoni_shahryar/41615 Jul 2026, 13:10 UTC | @sharyar_ir/1555 · this entry15 Jul 2026, 15:07 UTC | 1.00 | 1.9 hours |
| @taavoni_shahryar/42215 Jul 2026, 13:35 UTC | @sharyar_ir/1561 · this entry15 Jul 2026, 15:07 UTC | 1.00 | 1.5 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @taavoni_shahryar | 6 (6/6 hand-verifiable sample passed) | 1.00 | 2 minutes | @taavoni_shahryar (5–1) |
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 5 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 7 comparable posts for this entry, running 2 June 2026 to 15 July 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 @sharyar_ir — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 6 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 Aug 2026, 20:37 | 2,983 | +1 |
| 6 Aug 2026, 05:02 | 2,982 | no change |
| 6 Aug 2026, 03:59 | 2,982 | first reading |
7 posts held, back to 2 June 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 3 pagesof 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 7 posts for this entry, the most recent from 15 July 2026. An engagement rate over an empty window would be a number about nothing.
📸 گزارش تصویری۲ ا مجمع عمومی عادی سالیانه تعاونی شهریار با حضور نمایندگان منتخب اعضا، مجمع عمومی عادی سالیانه (نوبت اول ـ مرحله دوم) شرکت تعاونی تولیدی و توزیعی کارکنان شهرداری تهران (شهریار) برگزار شد. تصاویر پیشرو، گوشهای از این رویداد و مشارکت نمایندگان اعضا در فرآیند تصمیمگیری و ترسیم مسیر آینده تعاونی را به تصویر میکشد. ✳️شــَـهرْ-یـٰار؛خانوادهای به وسعت شهر 🆔@taavoni_shahryar
📸 گزارش تصویری۱ | برگزاری مجمع عمومی عادی سالیانه تعاونی شهریار مجمع عمومی عادی سالیانه (نوبت اول ـ مرحله دوم) شرکت تعاونی تولیدی و توزیعی کارکنان شهرداری تهران (شهریار) با حضور نمایندگان منتخب اعضا در تالار ایوان شمس برگزار شد ✳️شــَـهرْ-یـٰار؛خانوادهای به وسعت شهر 🆔@taavoni_shahryar
🔰مدیرعامل تعاونی شهریار خبرداد:درآمد ۲۹۶ میلیارد تومانی حاصل تلاش ۱۷ شرکت فعال است 🔹احسان عالیخانی،مدیرعامل شرکت تعاونی تولیدی و توزیعی کارکنان شهرداری تهران (شهریار)، با ارائه گزارشی از عملکرد سال مالی ۱۴۰۴ اظهار کرد: درآمد شرکت در سال گذشته به ۲۹۶ میلیارد تومان رسید که حاصل تلاش مستمر و فعالیت مؤثر ۱۷ شرکت فعال زیرمجموعه تعاونی است. 🔹وی در گزارش خود به مجمع عمومی عادی سالیانه (نوبت اول ـ مرحله دوم) شهریار که امرو…
🔰برگزاری مجمع عمومی عادی سالیانه تعاونی شهریار؛ تأیید عملکرد مالی و انتخاب بازرس قانونی 🔹مجمع عمومی عادی سالیانه (نوبت اول مرحله دوم) این شرکت با حضور نمایندگان منتخب اعضا در تالار ایوان شمس برگزار شد. 🔹به گزارش روابط عمومی شرکت تعاونی تولیدی و توزیعی کارکنان شهرداری تهران (شهریار)، در این مجمع، گزارش هیئتمدیره درباره عملکرد شرکت، گزارش بازرس قانونی و حسابرس مستقل و همچنین صورتهای مالی سال مالی منتهی به ۲۹ اسفندم…
🏴فرارسیدن تاسوعا و عاشورای حسینی ، سالروز شهادت سالار شهیدان حضرت اباعبدالله الحسین علیه السلام و یاران با وفایشان تسلیت باد. ✳️شــَـهرْ-یـٰار؛خانوادهای به وسعت شهر 🆔@taavoni_shahryar
با سلام و احترام لینــــــک کانال تعاونی شهریار تغییر کرده است جهت عضویت کلیک کنید👇🏻👇🏻👇🏻 @taavoni_shahryar @taavoni_shahryar @taavoni_shahryar @taavoni_shahryar
🔰فصل جدید توسعه برای پیک بادپا 🔹با تملک ۵۰ درصد از سهام شرکت پیک بادپا توسط گروه مالی شهر، همکاری راهبردی میان گروه مالی شهر، شهریار و پیک بادپا وارد مرحله جدیدی شد. 🔹احسان عالیخانی، مدیرعامل گروه شرکتهای شهریار، این مشارکت را نقطه عطفی برای توسعه خدمات حملونقل و توزیع شهری دانست و تأکید کرد که این همکاری میتواند مسیر رشد و ورود پیک بادپا به بازار سرمایه را هموار کند. 🔹علی بیگزاده، مدیرعامل گروه مالی شهر نیز ا…
Showing the 7 most recent of 7 posts we hold for @sharyar_ir. 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“شــَـهرْ-یـٰار (تعاونی کارکنانشهرداری تهران)” (@sharyar_ir), 2,983 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sharyar_ir.
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.