Channel
@ISFAutocom
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
90subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001112954673 |
|---|---|
| Type | Channel |
| Username | @ISFAutocom |
| Description | کانال رسمی نمایشگاه اتوکام اصفهان 🌎 http://autocom.ir 📞 031-36282881 |
| Created | Between 1 February 2017 and 31 January 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ISFAutocom |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 14:30 | 90 | no change |
| 6 Aug 2026, 15:06 | 90 | first reading |
20 posts held, back to 3 November 2019 — 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.
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 21 July 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The account of the user that owns this channel has been inactive for the last 11 months. If it remains inactive in the next 20 days, that account will self-destruct and this channel may no longer have an owner.
The account of the user that owns this channel has been inactive for the last 11 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
مدیرعامل سازمان فاوا شهرداری اصفهان: نمایشگاه اتوکام، فرصت مناسبی برای ارتباط بیشتر شهروندان با سامانه های شهروندي بود مطالعه متن کامل👇👇 https://b2n.ir/050786 @ictisfahan
حضور فعال سازمان فاوا و شهرداری اصفهان در نمایشگاه اتوکام 98 @ictisfahan
حضور فعال سازمان فاوا و شهرداری اصفهان در نمایشگاه اتوکام 98 @ictisfahan
مشارکت کنندگان گرامی در بیست و پنجمین نمایشگاه اتوکام اصفهان باعرض سلام بر خود لازم و واجب می دانم که از تک تک شما عزیزان که در برپایی شکوهمند بیست و پنجمین نمایشگاه اتوکام حضور یافتید کمال تقدیر و تشکر را داشته باشم . بی تردید بزرگترین رویداد فناوری اطلاعات و ارتباطات استان فقط با همت والای شما عزیزان که با تلاش و کوشش خود در سخت ترین شرایط اقتصادی مشارکت نمودید برگزار گردید . همواره این تجدید دیدارها برای ما…
✅ نمایشگاه اتوکام، یک قدم بلند برای اصفهان بود 🔸 کورش خسروی، رییس مرکز پژوهشهای شورای اسلامی شهر اصفهان در برنامه زنده تلویزیونی اینجا اصفهان: 🔻 برگزاری رویدادهایی مثل نمایشگاه اتوکام می تواند بسیار کمک کننده باشد چون جنب و جوش را در شهر افزایش می دهد. 🔻 کیفیت نمایشگاه اتوکام امسال بسیار بهتر بود و هر روز چندین برنامه آموزشی برگزار می شد. 🔻 از شرکت نمایشگاه های بین المللی استان اصفهان و سازمان نظام صنفی رایانه ا…
گفتگو با مهندس میرهادی معاون کارآفرینی و اشتغال اداره کار و رفاه اجتماعی استان اصفهان در نمایشگاه اتوکام @IsfAutocom
گفتگو با مهندس اطرج رییس سازمان نظام صنفی رایانه ای استان اصفهان در بیست و پنجمین نمایشگاه اتوکام @IsfAutocom
گزارش خبرگزاری صدا و سیما مرکز اصفهان از بیست و پنجمین نمایشگاه اتوکام @IsfAutocom
گزارش تصویری از حضور مسئولین استانی در بیست و پنجمین نمایشگاه اتوکام @IsfAutocom
Showing the 12 most recent of 20 posts we hold for @ISFAutocom. 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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Autocom” (@ISFAutocom), 90 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ISFAutocom.
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.