Telegram RegisterThe public register of Telegram
Telegram profile photo for مرکز تحقیقات ربات های دریایی

Channel

مرکز تحقیقات ربات های دریایی

@HU_Research_Center

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

54subscribers

+2 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003541919444
TypeChannel
Username@HU_Research_Center
Created17 February 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live8 November 2026
Measurements held3
Confirmed unchanged11 times, most recently 8 November 2026
On Telegramt.me/HU_Research_Center

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 47% 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 the other topics.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@YazdBlueCup/26116 Feb 2026, 20:12 UTC@HU_Research_Center/5 · this entry17 Feb 2026, 14:02 UTC1.0018 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@YazdBlueCup6 (6/6 hand-verifiable sample passed)1.009.5 hours@YazdBlueCup (6–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 1 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 17 February 2026 to 27 February 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @YazdBlueCup. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.

Growth

52545310 August 2026 — 52 subscribers10 August 2026 — 52 subscribers17 August 2026 — 54 subscribers10 August 202617 August 2026
3 measurements spanning 7 days, net +2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 52–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:2754+2
10 Aug 2026, 22:2152no change
10 Aug 2026, 15:0052first reading

Engagement

15 posts held, back to 17 February 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 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 15 posts for this entry, the most recent from 27 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
12m 54s
Average length
2m 09s

Measured directly from 6 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.

Reaction mix

8 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤562.5%
🔥225.0%
🐳112.5%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 15 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 February 2026 to 27 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

27 Feb 2026, 17:17 UTC40 viewsread 10 August 2026
Forwarded from @YazdBlueCupPhoto

🔶🔸همایش معرفی رویداد «جام آبی یزد ۱۴۰۵»🔸🔶 اگر درباره رویداد «جام آبی یزد ۱۴۰۵» سوالی دارید، این همایش برای شماست. در این همایش مجازی، به صورت شفاف به پرسش‌ها و ابهامات پاسخ داده می‌شود. 🔷 موضوعات این جلسه: 🔹 «جام آبی یزد ۱۴۰۵» چیست و با چه هدفی برگزار می‌شود؟ 🔹 ساختار رویداد و روند اجرایی آن چگونه است؟ 🔹 مراحل این رویداد ۸ ماهه چیست؟ 🔹 آیا این رویداد متناسب با اهداف شماست؟ 🔹 با شرکت در آن چه دستاوردهایی خواهید داشت…

26 Feb 2026, 14:21 UTC66 viewsread 10 August 2026
Forwarded from @YazdBlueCup

👇🏻از اینجا استارت بزن، تیمت رو بساز 👇🏻 🔹 اگر به کار تیمی مهندسی و تجربه یک رقابت ملی علاقه‌مند هستید، جام آبی یزد ۱۴۰۵ می‌تونه یک فرصت جدی برای شما باشه؛ مسیری هشت ماهه در حوزه طراحی و ساخت ربات‌های بدون سرنشین دریایی و تجربه یک تابستان پرچالش 🔥 🔸 اگر هنوز داری به این فکر می‌کنی که... من کجا و این مسیر کجا، کمتر از یک دقیقه زمان بذار و پرس‌لاین رو تکمیل کن. 🔗 https://survey.porsline.ir/s/X9GvT6p6 …

26 Feb 2026, 06:26 UTC80 viewsread 10 August 2026
Video

🎥 نمایی از رقابت‌های جام آبی یزد ۱۴۰۲ 🌊 در سال ۱۴۰۲ علاوه بر اجرای مسابقات در استخرهای دانشگاه یزد، اغلب تیم‌ها و همه‌ی ربات‌ها، برای اولین بار یک اجرای واقعی در محیط کنترل‌نشده‌‌ی دریایی (خلیج فارس) را تجربه کردند. می‌شود تعریف گام سوم را بزرگترین تفاوت مسابقات ۱۴۰۲ نسبت به دوره قبل دانست. 🚢 پایش کشتی غرق شده نزدیک جزیره هرمز، طی مسافت‌های کیلومتری در معرض امواج دریا و حتی اجرای مانورهای ناوبری اتوماتیک در تاریکی…

25 Feb 2026, 20:20 UTC72 viewsread 10 August 2026
Video

🎥 نمایی از رقابت‌های جام آبی یزد ۱۴۰۲ 🔻 در سال ۱۴۰۲ تصمیم بر آن شد که میزبان تیم‌هایی از دانشگاه‌های سراسر کشور باشیم. در این رقابت ۳۷ تیم حضور داشتند. 🔻 مسابقات در قالب یک لیگ عمومی برگزار شد اما با اضافه شدن قابلیت ناوبری اتوماتیک مبتنی بر مختصات ربات‌ها، در گام دوم مسابقات، علاوه‌بر استخر سرپوشیده، استخر روباز دانشگاه یزد هم میزبان تیم‌های رباتیک دریایی ایران بود. 🐳 جام آبی یزد | Yazd Blue Cup 🔗 @YazdBlueCup 🌐…

25 Feb 2026, 20:20 UTC72 viewsread 10 August 2026

📌 در این دوره از مسابقات، محدوده وزنی ربات‌ها بین ۱۰ تا ۳۰ کیلوگرم شد، بنابراین شاهد ربات‌های بزرگتر و جدی‌تری نسبت به قبل بودیم. ⚙ عملیات‌هایی که تعریف شده‌بودند عملاً ربات‌ها رو به سمت و سوی کاربردی‌تر شدن سوق دادند و اغلب تیم‌ها ابزاری برای برداشتن و جابه‌جایی بار هم به ربات اضافه کرده‌بودند. 🕹 در این دوره از رقابت‌ها باتوجه به ضریب کاهشی قابل توجه روی امتیاز برای ربات‌هایی که با دید مستقیم اوپراتور کنترل می‌شدن…

24 Feb 2026, 16:25 UTC66 viewsread 10 August 2026

📌 در مسابقات سال ۱۴۰۱ تنها محدودیتی که ربات ها داشتند وزن آنها بود، اما ربات‌ها در انتخاب طرح، شکل و جنس بدنه، نوع و تعداد تراستر، نوع تغذیه (درونی یا بیرونی با سیم) و نوع ارتباط (بی‌سیم یا باسیم) محدودیتی نداشتند. 🧑🏻‍💻 تیم‌ها طی حدود ۴ ماه تلاش مستمر در بازه تیر تا آبان ۱۴۰۱، با تکیه بر یادگیری‌های آکادمیک دانشگاهی و آزاد غیردانشگاهی، توانستند محصول خود را برای شرکت در مسابقات نهایی کنند.

24 Feb 2026, 16:25 UTC70 viewsread 10 August 2026
Video

🎥 نمایی از رقابت‌های جام آبی یزد ۱۴۰۱ 🖇 ویدیویی که مشاهده می‌کنید، اولین رقابت ۱۱ ربات‌ دریایی در "جام آبی یزد ۱۴۰۱" است که داخل استخر سرپوشیده دانشگاه یزد برگزار شد. 🔹 مسابقات در قالب یک لیگ عمومی با عنوان "ربات‌های متحرک دریایی" برگزار شد که طی آن، عملیات و مانورهایی روی سطح آب و هم زیر آب، با کنترل دستی توسط اوپراتور انجام شد. 🐳 جام آبی یزد | Yazd Blue Cup 🔗 @YazdBlueCup 🌐 YazdBlueClub.com 📬 @YazdBlueCup_Admin

21 Feb 2026, 08:24 UTC104 views3 reactionsread 10 August 2026
Forwarded from @YazdBlueCupVideo

🔷 لیگ IP به روایت تیم‌های شرکت‌کننده در جام آبی یزد ۱۴۰۳ 🔹 در این لیگ، تیم‌ها مسئول پردازش داده‌های تصویری دریافت‌شده از دوربین ربات هستند؛ استخراج ویژگی‌ها، تشخیص اهداف و تولید فرامین متناسب با نتایج تشخیص، هسته اصلی رقابت در این بخش را تشکیل می‌دهد. 🔹 در روند اجرای آیتم‌های مسابقه مفاهیمی چون: - پردازش تصویر در شرایط واقعی محیطی (نور، اعوجاج و نویز)، - استخراج ویژگی و تشخیص اشیاء و الگوها، - تفکیک و طبقه‌بندی اهد…

🔥2❤1

19 Feb 2026, 10:32 UTC95 views2 reactionsread 10 August 2026
Forwarded from @YazdBlueCupVideo

🔷 لیگ USV به روایت تیم‌های شرکت‌کننده در جام آبی یزد ۱۴۰۳ 🔹 در این لیگ، رقابت میان ربات‌های سطحی بدون سرنشین است که قابلیت کنترل از راه دور توسط اپراتور را دارند و همچنین می‌توانند مأموریت‌های ناوبری خودکار از پیش‌تعریف‌شده را اجرا کنند. 🔹 در روند اجرای آیتم‌های مسابقه مفاهیمی چون: - مانورپذیری، پایداری، چابکی، برد و سرعت، - رابطه مؤثر ربات و اوپراتور به واسطه هدایت مبتنی بر دید اول شخص و یا هدایت مبتنی بر مختصات، …

❤2

18 Feb 2026, 16:46 UTC91 views1 reactionsread 10 August 2026
Forwarded from @YazdBlueCupVideo

🔷 لیگ ROV به روایت تیم‌های شرکت‌کننده در جام آبی یزد ۱۴۰۳ 🔹 در این لیگ، ربات‌های زیرسطحی که توسط اپراتور کنترل می‌شوند، در اجرای مأموریت‌های تعریف‌شده با یکدیگر رقابت می‌کنند. 🔹 در روند اجرای آیتم‌های مسابقه مفاهیمی چون: - مانورپذیری، پایداری، چابکی و عملیات در عمق، - رابطه مؤثر ربات و اوپراتور به واسطه هدایت مبتنی بر دید اول شخص، - جست‌و‌جو و شناسایی، - برداشت، حمل و گذاشت بار - ثبت مختصات و داده‌ی سایر سنسورهای م…

❤1

17 Feb 2026, 14:02 UTC139 views2 reactionsread 10 August 2026

🔰 سه لیگ، سه گام 🔰 🔹 دوره پنجم جام آبی یزد در قالب سه لیگ تخصصی و طی سه گام مرحله‌ای برگزار می‌شود. 🔹 هر تیم در ابتدای مسیر، در گام اول یک لیگ را انتخاب می‌کند و رقابت را تا پایان گام دوم و سوم، در همان مسیر تخصصی ادامه می‌دهد. 🔹 لیگ‌های سه‌گانه شامل دو لیگ پلتفرمی و یک لیگ زیرسیستمی توسعه‌ی نرم است. 🔶 لیگ‌های پلتفرمی 🔶 در لیگ‌های پلتفرمی، تیم‌ها مسئول توسعه یک ربات متحرک دریایی کامل هستند؛ از طراحی مهندسی تا ساخ…

❤1🐳1

17 Feb 2026, 13:57 UTC124 viewsread 10 August 2026

سلام و عرض ادب لطفاً لینک کانال رو برای دوستانتون که میدونید علاقه مند هستند بفرستید. ممنون.

Showing the 12 most recent of 15 posts we hold for @HU_Research_Center. 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.

Forward network

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.

Mentions

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.

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.

Cite this entry

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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“مرکز تحقیقات ربات های دریایی” (@HU_Research_Center), 54 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/HU_Research_Center.

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.