Channel
@RoboSkills_iran
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
549subscribers
+6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001105055506 |
|---|---|
| Type | Channel |
| Username | @RoboSkills_iran |
| Created | Between 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 4 times, most recently 16 September 2026 |
| On Telegram | t.me/RoboSkills_iran |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 00:24 | 549 | +2 |
| 15 Aug 2026, 18:17 | 547 | +3 |
| 7 Aug 2026, 11:34 | 544 | +1 |
| 6 Aug 2026, 18:18 | 543 | no change |
| 6 Aug 2026, 17:59 | 543 | first reading |
12 posts held, back to 26 September 2024 — 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 12 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
اطلاعیه : هشتمین دوره مسابقات RoboSkills کرمان در تاریخ ۱۶ الی ۱۹ شهریور در دو لیگ نبرد ربات ها وزن ۶ و ۱.۵ کیلوگرم و لیگ نبرد نخبگان ایران برنامه ریزی شده است اما شرایط کشور طوری است که اجازه اطلاع رسانی قطعی را به دبیرخانه نداده اند . لذا از تیم های علاقه مند جهت حضور در این رویداد تقاضا می شود تا زمان قطعی نشدن برگزاری در تاریخ مذکور اقدام خاصی ننمایند . بلافاصله که مجوز برگزاری صادر گردد قوانین پوستر و سایر ا…
تشریح پیش نویس قوانین مسابقات نبرد نخبگان ایران Roboskills یکشنبه ۲۱ تیر راس ساعت ۱۸:۳۰ در محل خانه خلاق و نوآوری فرامهارت برگزار می گردد .
به زودی جزییات مسابقات فناوری و نوآوری RoboSkills 2026 کرمان اعلام خواهد شد . منتظر خلق رقابتی هیجان انگیز ، نوآورانه و خلاقانه با مهارت ها و فناوری های نو ظهور باشید .
این هفته میزبان همه شما فناوران و نوآوران شهر کرمان هستیم
جوایز هفتمین دوره مسابقات رباتیک RoboSkills به مجموع 200 میلیون تومان واریز گردید . با عرض پوزش بابت تاخیر در پرداخت ها
⚡️The second qualifying stage of the Battle of Robots is over. Everything was just the way we like it: sparks, smoke and robots flying apart! 8 teams from the category up to 110 kg entered the next stage: 1. Daddy Bots (Saint Petersburg) 2. WEBER LABS (Moscow) 3. Hypericum (Perm) 4. Lavan Team (Kerman, Iran) 5. Energy Girls (Saint Petersburg) 6. SOLARBOT (Balashikha) 7. Ice Orange (Harbin, China) 8. PY Roboticsz (Pu…
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Video, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 12 posts we hold for @RoboSkills_iran. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“RoboSkills Robotics Competitions” (@RoboSkills_iran), 549 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/RoboSkills_iran.
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.