Channel
@Arcims27_kmu
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,699subscribers
+55 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003333460786 |
|---|---|
| Type | Channel |
| Username | @Arcims27_kmu |
| Created | Between 1 November 2025 and 31 March 2026— 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 | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Arcims27_kmu |
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 77% 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 |
|---|---|---|---|
| @Arcims27_kmu/110 · this entry28 Jul 2026, 18:26 UTC | @student_research_committeee/216628 Jul 2026, 18:27 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @student_research_committeee | 7 (7/7 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6–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 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 18 comparable posts for this entry, running 25 July 2026 to 7 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 @Arcims27_kmu — which is this entry. That is a statement about our reading window, not a claim of authorship.
3,850 average views per post against 1,699 subscribers — an engagement rate of 226.8%. Across the 15,813 registered channels in the same cohort — 1,000–3,162 subscribers, posting mainly in Persian — the middle half sit between 8.34% and 32.3%, with a median of 17.2%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 23 of 24 published in the window (5 exact, 18 rounded by Telegram) |
| Views totalled | 88,630 |
| Mature posts only | 243.0% over 21 posts read at least 24h after publication |
| Subscribers | 1,699 measured 12 August 2026 |
| Cohort | b1000:fas · 15,813 channels · p10 3.91% · p25 8.34% · p50 17.2% · p75 32.3% · p90 53.6% |
| Position in cohort | 99.450th percentile · 13.2× the cohort median |
| Uncertainty | ±0.17% of the figure, from Telegram’s rounding |
| Post language | Persian · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_source · err_high, last confirmed 12 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 |
|---|---|---|
| 12 Aug 2026, 00:42 | 1,699 | +17 |
| 9 Aug 2026, 05:03 | 1,682 | +23 |
| 6 Aug 2026, 15:16 | 1,659 | +15 |
| 6 Aug 2026, 07:19 | 1,644 | no change |
| 6 Aug 2026, 02:18 | 1,644 | first reading |
24 posts held, back to 25 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 2 pagesof 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 7 August 2026 |
|---|---|
| Posts held | 24 (25 July 2026 – 7 August 2026) |
| Views total | 88,630 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:51 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.
Measured directly from 2 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.
🌱 یک ایده علمی هر چقدر هم که جذاب باشد، بدون درک درست از بازار، به محصول تبدیل نمیشود... دبیرخانه ۲۷ـمین کنگره ملی و ۱۳ـمین کنگره بینالمللی پژوهش و فناوری دانشجویان علوم پزشکی کشور وبینار «توسعه محصول از دریچه بازار» مدرس: جناب آقای دکتر عمید رهی «استادیار نانوفناوری پزشکی» «عضو هیات علمی دانشکده پزشکی افضلی پور و مرکز تحقیقات پاتولوژی و سلول های بنیادی» لینک ثبتنام: اینجا لینک برگزاری : اینجا یکشنبه ۱۸ مر…
‼️ کمتر از ۶ ساعت تا پایان جشنواره کارمانیا !! جناب آقای امیر طالبیان ــ دبیر جشنواره کارمانیا ــ دانشجوی داروسازی ــ استاد ممتاز خوشنویسی 👇🏻فرصت را از دست ندهید... @Arcims27_kmu 🌱 دبیرخانه بیست و هفتمین کنگره ملی و سیزدهمین کنگره بینالمللی سالیانه دانشجویی علوم پزشکی کشور
‼️ کارگاه در حال برگزاری...
🌱 یادآوری کارگاه «هنر ارائه ؛ اصول ارائه و سخنرانی (ویژه کنگره ها)» ✨ساعت ۱۸ لینک وبینار
‼️ تنها ۱ روز تا پایان جشنواره !! 👇🏻فرصت را از دست ندهید... ✨ @Arcims27_kmu/119 🌱 دبیرخانه بیست و هفتمین کنگره ملی و سیزدهمین کنگره بینالمللی سالیانه دانشجویی علوم پزشکی کشور
📢 اطلاعیه مهم دبیرخانه کنگره با سلام و احترام به اطلاع کلیه پژوهشگران، دانشجویان و علاقهمندان به شرکت در بیستوهفتمین کنگره ملی و سیزدهمین کنگره بینالمللی سالیانه پژوهش و فناوری دانشجویان علوم پزشکی کشور میرساند: پیرو نامه ارسالی به واحدهای امور بینالملل دانشگاههای علوم پزشکی، به آگاهی میرساند مهلت ارسال چکیده مقالات تا تاریخ ۲۵ مردادماه صرفاً برای دانشجویان بینالملل (دانشجویان غیرایرانی) و با هدف تسهیل و ا…
با سلام و احترام؛ به استحضار میرساند ویدئوهای ضبطشده کارگاههای آموزشی برگزار شده، جهت بهرهبرداری علمی، به تاریخ برگزاری به ترتیب ذیل در دسترس میباشد: ۱. نحوه نگارش خلاصه مقالات ویژه کنگره لینک دسترسی ۲. از ایده تا پروپوزال ، مسیر تدوین طرح پژوهشی لینک دسترسی ۳. Clear and scientific writing لینک دسترسی ۴. راهکار های افزایش مقاومت روانی در برابر مشکلات به زودی ۵. سرآمدی و مرجعیت علمی به زودی ۶. Systematic R…
دبیرخانه ۲۷ـمین کنگره ملی و ۱۳ـمین کنگره بینالمللی پژوهش و فناوری دانشجویان علوم پزشکی کشور کرمان- ۱۴۰۵ با همکاری کمیته های تحقیقات و فناوری کلان منطقه 8: وبینار «هنر ارائه ؛ اصول ارائه و سخنرانی علمی» مدرس: دکتر مسعود رضایی پزشک عمومی _ پژوهشگر مرکز تحقیقات بیماری هیداتید دانشگاه علوم پزشکی کرمان ️ زمان: پنج شنبه ۱۵ مرداد ماه ۱۴۰۵ ساعت : ۱۸:۰۰ لینک ثبت نام : اینجا لینک برگزاری: sr.kmu.ac.ir/ch/vresea…
🌱 یادآوری کارگاه.. ‼️حضور در وبینار امروز جهت تکمیل فرآیند ارزیابی الزامی میباشد. ساعت ۱۷ https://t.me/Arcims27_kmu/118
تا ۱۶ مرداد تمدید شد ❗️❗️ جشنواره علمی هنری «کارمانیا» 🌱 از سبزی پسته تا سرخی پرچم همزمان با بیستوهفتمین کنگره ملی و سیزدهمین کنگره بینالمللی سالیانه پژوهش و فناوری دانشجویان علوم پزشکی کشور در کرمان 👤 مخاطبین: اساتید، کارکنان و دانشجویان علوم پزشکی سراسر کشور 🔹 محورهای جشنواره: 🌍 میراث آینده؛ محیط زیست و توسعه پایدار 🩺 کادر سلامت؛ روایتگران حیات 🚀 ایران آینده؛ افقهای سلامت و نوآوری بخش ویژه: جوانی جمعیت؛ س…
✨ فاصله میان یک «مشکل ساده» و یک «ثروت پایدار»، یک طراحی هوشمندانه است... دبیرخانه ۲۷ـمین کنگره ملی و ۱۳ـمین کنگره بینالمللی پژوهش و فناوری دانشجویان علوم پزشکی کشور «از مسئله تا بازار؛ طراحی مدل کسبوکار» مدرس: جناب آقای دکتر محمدرضا رجبعلیپور «دکترای تخصصی آموزش بهداشت و ارتقای سلامت» «استادیار دانشکده بهداشت» «مدیر فناوری پارک علم و فناوری سلامت استان کرمان» لینک ثبت نام: اینجا لینک برگزاری کارگاه: اینجا شن…
‼️ اطلاعیه مهم | ویژه تیمهای استارتاپی بخش فناوری با سلام و احترام ، به اطلاع تمامی شرکتکنندگان محترم میرساند، تکمیل موارد زیر برای تمام اعضای تیمها الزامی بوده و در ارزیابی نهایی تیمها تأثیر مستقیم خواهد داشت. ۱. تکمیل فرم ارزیابی فرم ارزیابی در اختیار شما قرار گرفته است. تمامی اعضای تیم موظفاند این فرم را بهطور کامل تکمیل و ارسال کنند. ۲. بارگذاری کلیپ معرفی (حداکثر ۱ دقیقه) هر عضو تیم باید یک ویدئوی حد…
Showing the 12 most recent of 24 posts we hold for @Arcims27_kmu. 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.
Citation-graph rank — 218 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 102 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@Arcims27_kmu named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“27th . ARCIMS . KERMAN” (@Arcims27_kmu), 1,699 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Arcims27_kmu.
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.