Channel
@saramad_hr
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
371subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001043316658 |
|---|---|
| Type | Channel |
| Username | @saramad_hr |
| Created | Between 1 January 2016 and 31 October 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/saramad_hr |
Education — 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 99% 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. They sit inside a group of 3 channels that share the same post bodies with each other. 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 |
|---|---|---|---|
| @Saramad_HRD/454031 Jul 2026, 05:33 UTC | @saramad_hr/2163 · this entry31 Jul 2026, 05:39 UTC | 1.00 | 6 minutes |
| @Saramad_HRD/45502 Aug 2026, 03:34 UTC | @saramad_hr/2173 · this entry2 Aug 2026, 03:49 UTC | 1.00 | 14 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Saramad_HRD | 10 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @Saramad_HRD (10–0) |
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 0 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 11 comparable posts for this entry, running 30 July 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 3, the earliest publisher we hold is @Saramad_HRD. 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 2 other registered channels, 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 |
|---|---|---|
| 14 Aug 2026, 12:46 | 371 | +1 |
| 6 Aug 2026, 20:47 | 370 | no change |
| 6 Aug 2026, 00:04 | 370 | first reading |
11 posts held, back to 30 July 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 11 (30 July 2026 – 6 August 2026) |
| Views total | 133 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 20:47 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.
اگر مدرک تحصیلی شما کمتر از شرایط احراز شغل باشد، چند سال سابقه کار باید داشته باشید تا این کمبود جبران شود؟ ❗️نکته مهم: در مورد مدارک تحصیلی بالاتر از دیپلم و دانشگاهی هر یکسال و نیم تجربه جایگزین یک سال کمبود مدرک تحصیلی خواهد شد. www.tamasco.ir 📧[email protected] ☎️۰۲۱-۲۶۴۰۱۳۳۵ ۰۲۱-۲۶۷۰۹۱۵۱
Signed آرمین خوشوقتی
برای مادرانی که پس از پايان مرخصی زايمان، به كار سابق خود باز میگردند، پرداخت کمک عائلهمندی بر عهده کیست؟ این کمک عائلهمندی از چه تاریخی باید پرداخت شود؟ از زمان تولد؟ یا از زمان بازگشت بهکار؟ دریافت مشاوره قانون کار و تامین اجتماعی از طریق لینک زیر👇 https://tamasco.ir/product/request-hr-consulting/
Signed آرمین خوشوقتی
بازخورد مؤثر یعنی درباره رفتار حرف بزنیم، نه شخصیت. شفاف باشیم، مثال مشخص بزنیم و گفتوگو را با یک قدم عملی تمام کنیم. ارزیابی عملکرد وقتی ارزشمند است که به رشد کمک کند، نه اینکه فقط ایرادها را یادآوری کند. بهنظر شما مهمترین ویژگی یک بازخورد خوب چیست؟ https://tamasco.ir/courses/مدیریت-عملکرد-کارکنان-بر-اساس-مدل-ttm/
Signed آرمین خوشوقتی
خروج یک کارمند فقط پایان یک همکاری نیست؛ فرصتی است برای یادگیری. مصاحبه خروج، یکی از ارزشمندترین ابزارها برای شناخت نقاط قوت و ضعف سازمان است. گاهی مهمترین بازخوردها را کسی میدهد که در حال ترک مجموعه است. مدیران هوشمند، از هر خداحافظی یک فرصت برای رشد میسازند. 🌱 شما چقدر به نظرات کارکنانی که از سازمان خارج میشوند اهمیت میدهید؟ نظرتان را در کامنتها بنویسید. 👇 📌 اگر این مطلب برایتان مفید بود، آن را برای مدیران، ک…
Signed آرمین خوشوقتی
همهچیز درباره مشاغل سختوزیانآور 🔹️چه مرجعی درباره گروه الف یا ب بودن یک شغل تصمیم میگیرد؟ 🔸️وظایف کارفرما در مشاغل سخت و زیانآور گروه الف و ب 🔹️آیا مشاغل سختوزیانآور قابل رفع هستند؟ https://tamasco.ir/مشاغل-سخت-و-زیان-آور-گروه-الف-و-ب/
Signed آرمین خوشوقتی
علل اصلی طولانی شدن زمان رسیدگی به پروندههای إدارات کار بالاترین کیفیت رسیدگی به دعاوی کارگری-کارفرمایی مربوط به کدام استان است؟ در این گفتوگو، از سه پرونده واقعی گفتهام: 🔹 یک خانم خانهدار که بدون وکیل، حق خود را از سازمان تامین اجتماعی گرفت. 🔹 یک شرکت بزرگ خودروسازی که به دلیل ناآگاهی از قانون، پرونده را به یک کارگر تولید باخت. 🔹 یک دکتر داروساز که بدون تحصیلات حقوقی، با مطالعه دقیق قوانین، تمام مطالبات خود را…
Signed آرمین خوشوقتی
هر سازمانی، صرفنظر از صنعت فعالیتش، زمانی میتواند تصمیمات دقیقتری در حوزه منابع انسانی بگیرد که جایگاه و ارزش هر شغل بهصورت شفاف مشخص شده باشد. در پروژه طبقهبندی مشاغل شرکت تجارت فناوری اطلاعات همفکران تفاهم، مشاغل سازمان با استفاده از روش سنتی طبقهبندی مشاغل مورد بررسی، تحلیل و ارزشیابی قرار گرفتند تا ساختاری منسجم برای مدیریت مشاغل و نظام پرداخت ایجاد شود. نتیجه این پروژه، ایجاد شفافیت در ساختار مشاغل، تسهیل …
Signed آرمین خوشوقتی
اصل بیطرفی مراجع حل اختلاف کار در معرض خطر استفاده از ظرفیت کارشناسان سازمان تامین اجتماعی (جهت عضویت در مراجع حل اختلاف کار)، اقدامی ارزشمند و قابل حمایت است. اما آیا عضویت کارکنان این سازمان در مراجع حل اختلاف کار، با اصل بیطرفی این مراجع سازگار است؟ تفاهمنامه جدید وزارت تعاون، کار و رفاه اجتماعی و سازمان تامین اجتماعی، این پرسش را مطرح میکند که آیا این تفاهمنامه میتواند به ارتقای کیفیت رسیدگیها کمک کند یا …
Signed آرمین خوشوقتی
نرخ شبکاری چقدر است؟ سی و پنج درصد؟ یا صد و سی و پنج درصد؟ https://tamasco.ir/product/request-hr-consulting/ مشاوره قانون کار و تامین اجتماعی 👆
Signed آرمین خوشوقتی
🔻چرا تیم شما خوب کار نمیکند؟ چون انتظارها واضح نیست، هدفها گنگاند و بازخورد بهموقع داده نمیشود. اما خبر خوب اینجاست… 🎯 در دوره مدیریت عملکرد یاد میگیرید: چطور اهداف را حرفهای تعیین کنید، عملکرد واقعی را اندازهگیری کنید، مکالمات سخت را مدیریت کنید و از هر کارمند «بیشترین خروجی» را بگیرید—بدون تنش و فرسودگی. 🚀 اگر مدیر هستید و میخواهید تیمی بسازید که بجنگد، نتیجه بدهد و مسئولیتپذیر باشد یا اگر HR هستید و می…
Signed آرمین خوشوقتی
درباره قرادادهای خطرناک سفیدامضا چه اطلاعاتی دارید؟ در این گفتگویرادیویی، به تبعات قانونی قرادادها و اسناد سفیدامضا پرداختیم. مشاوره قانون کار، تامین اجتماعی و مشاغل سختوزیانآور 👇 https://tamasco.ir/product/request-hr-consulting/ ۰۲۱-۲۶۴۰۱۳۳۵ ۰۲۱-۲۶۷۰۹۱۵۱ ☎️
Signed آرمین خوشوقتی
Showing the 11 most recent of 11 posts we hold for @saramad_hr. 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“آموزش منابع انسانی سرآمد” (@saramad_hr), 371 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/saramad_hr.
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.