Telegram RegisterThe public register of Telegram
Telegram profile photo for YazdBlueCup

Channel

YazdBlueCup

@YazdBlueCup

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

657subscribers

-32 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002372375087
TypeChannel
Username@YazdBlueCup
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/YazdBlueCup

Topic

Education — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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/261 · this entry16 Feb 2026, 20:12 UTC@HU_Research_Center/517 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
@HU_Research_Center6 (6/6 hand-verifiable sample passed)1.009.5 hoursthis entry (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 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 9 February 2026 to 2 June 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 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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

6576896736 August 2026 — 689 subscribers6 August 2026 — 689 subscribers13 August 2026 — 687 subscribers20 August 2026 — 683 subscribers28 August 2026 — 678 subscribers4 September 2026 — 675 subscribers13 September 2026 — 672 subscribers26 September 2026 — 667 subscribers7 October 2026 — 661 subscribers14 October 2026 — 659 subscribers22 October 2026 — 661 subscribers29 October 2026 — 659 subscribers12 November 2026 — 657 subscribers6 August 202612 November 2026
13 measurements spanning 98 days, net -32. 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 652–694 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 12:11657-2
29 Oct 2026, 00:51659-2
22 Oct 2026, 17:48661+2
14 Oct 2026, 19:27659-2
7 Oct 2026, 12:20661-6
26 Sept 2026, 06:56667-5
13 Sept 2026, 13:00672-3
4 Sept 2026, 18:58675-3
28 Aug 2026, 11:05678-5
20 Aug 2026, 11:23683-4
13 Aug 2026, 14:17687-2
6 Aug 2026, 16:38689no change
6 Aug 2026, 05:18689first reading

Engagement

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

Recent posts

2 Jun 2026, 13:04 UTC325 viewsread 6 August 2026
Forwarded from @YazdEnginexMindsPhoto

رویداد Yazd EngiNEX Minds یزد آینده؛ ذهن‌های مهندسی

2 Jun 2026, 13:04 UTC362 viewsread 6 August 2026
Forwarded from @YazdEnginexMinds

رویداد Yazd EngiNEX Minds یزد آینده؛ ذهن‌های مهندسی 💠 رویداد فشرده تابستانه مهندسی محصول انجی‌نکس در تابستان ۱۴۰۵ برگزار می‌شود. 🔹 این رویداد، یک برنامه فشرده آموزشی، تمرین و تجربه دانشجویی پروژه‌محور است که با رویکرد عملی و مهندسی و پس‌زمینه رباتیک و مکاترونیک، در تابستان و به‌صورت حضوری در دانشگاه یزد برگزار می‌شود. 🔹 محتوای رویداد شامل ➕ مقداری آموزش‌های فنی پایه و تخصصی ➕ آموزش روند مهندسی سیستم ➕ تمرین مهارت…

2 Jun 2026, 13:04 UTC295 viewsread 6 August 2026
Forwarded from @YSB_CUPPhoto

🏜 سفری از ایده تا ساخت، در قلب کویر… 🤖 جام ربات‌های شنی یزد ۱۴۰۵ (Yazd Sandbot Cup 2026) فقط یک مسابقه ساده نیست؛ یک سفر مهندسی است! قراره در این رویداد دانشجویی، قدم‌به‌قدم درگیر یک چالش واقعی بشیم. از ایده‌پردازی و طراحی گرفته تا دست‌به‌آچار شدن و ساخت صفر تا صد یک ربات متحرک زمینی (UGV). 📱 💡 توی این مسیر هیجان‌انگیز قراره چی به دست بیاریم؟ 🟦 تجربه بی‌نظیر کار تیمی و حل مسئله 🟦 ارتقای چشمگیر مهارت‌های فنی و عملی…

2 Jun 2026, 13:03 UTC380 viewsread 6 August 2026

🔹️ تابستان امسال، بدون جام آبی اما فشرده و پرکار تابستان امسال، در دانشگاه یزد دو برنامه محلی با هدف تجربه انجام یک پروژه واقعی به عنوان مکمل آموزش‌های رسمی دانشگاه ارائه می‌شود: - رویداد انجی‌نکس (یزد آینده؛ ذهن‌های مهندسی) - رویداد جام ربات‌های شنی این رویدادها با این نگاه طراحی شدن تا افراد و تیم‌ها رو به سمت فعالیت‌های فناورانه و تشکیل واحدهای فناور هدایت کنن. به دلیل محدودیت شدید در تأمین اسکان، احتمالاً …

18 May 2026, 15:34 UTC693 viewsread 6 August 2026
Photo

🪧 اطلاعیه لغو رویداد «جام آبی یزد ۱۴۰۵» 🔹 به اطلاع مخاطبان محترم رویداد می‌رساند: با توجه به شرایط کشور و دستورالعمل‌ها که امکان اجرای رویداد گسترده ملی به صورت حضوری را ممکن نمی‌سازد، علیرغم تلاش‌های کمیته برگزاری برای بازطراحی برنامه‌های پشتیبانی، فراهم نمودن مقدمات و حفظ آمادگی برای ورود فوری به فرآیند اجرای رویداد در صورت تغییر شرایط، با عبور از آخرین فرصت ممکن برای شروع، برگزاری رویداد جام آبی یزد در سال جاری ل…

4 Mar 2026, 13:11 UTC677 viewsread 6 August 2026

🪧 اطلاعیه 🔹 باتوجه به شرایط کشور، اختلال در اینترنت و بسترهای تعامل (به‌ویژه گوگل میت)، به اطلاع مخاطبین محترم رویداد می‌رساند: ثبت‌نام گام اول جام آبی یزد ۱۴۰۵ و سایر برنامه‌ها و جلسات به مدت یک هفته معلق اعلام می‌شود. 🔹 به محض تغییر شرایط، زمان‌بندی رویداد به‌روزرسانی و متعاقباً اعلام می‌شود. فعلا لغو رویداد مطرح نیست. 🐳 جام آبی یزد | Yazd Blue Cup سری مسابقات ملّی ربات‌های بدون سرنشین دریایی 🔗 @Yaz…

28 Feb 2026, 10:54 UTC725 viewsread 6 August 2026

📣 با توجه به شرایط جدید کشور، برنامه‌ها و جلسات رویداد برای امروز و فردا شنبه ۱۲/۰۹ و یکشنبه ۱۲/۱۰ لغو شده است. 🔹️ در صورت تغییر شرایط، فعالیت‌ها مجددا برنامه‌ریزی و اعلام خواهد شد. 🐳 جام آبی یزد | Yazd Blue Cup سری مسابقات ملّی ربات‌های بدون سرنشین دریایی 🔗 @YazdBlueCup 🌐 YazdBlueClub.com 📬 @YazdBlueCup_Admin

26 Feb 2026, 14:17 UTC≈2,580 viewsread 6 August 2026
Photo

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

25 Feb 2026, 20:17 UTC725 viewsread 6 August 2026

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

24 Feb 2026, 19:31 UTC990 viewsread 6 August 2026
Video

با شرکت در کارگاه حضوری نوروز، گام اول را قوی بردارید. 🔶 در کارگاه حضوری نوروز: 🔸 کار تیمی واقعی را تجربه می‌کنید، 🔸 در ارائه‌های موضوعی شرکت می‌کنید، 🔸 نمونه ربات‌های سال‌های قبل را می‌بینید و 🔸 با کمک منتورها، طراحی مفهومی‌تان را کامل می‌کنید. 📆 ۷ تا ۱۴ فروردین ۱۴۰۵ ⏰ ۸:۰۰ تا ۲۰:۰۰ 🗺 دانشگاه‌ ‌یزد 🐳 جام آبی یزد | Yazd Blue Cup سری مسابقات ملّی ربات‌های بدون سرنشین دریایی 🔗 @YazdBlueCup 🌐 YazdBlueClu…

24 Feb 2026, 16:54 UTC≈1,060 viewsread 6 August 2026

🔰 گام اول | نقطه آغاز یک مسیر مهندسی 🔰 🔷 گام اول جام آبی یزد ۱۴۰۵، نقطه‌ی ورود تیم‌ها به مسیر حرفه‌ای توسعه ربات‌های دریایی است؛ جایی که نه فقط یک طرح، بلکه مسیر تبدیل یک مفهوم مهندسی به یک سامانه عملیاتی ترسیم می‌شود. 🔶 در این گام: 🔸 لیگ تخصصی خود را انتخاب می‌کنید، 🔸 با چالش‌های طراحی سیستم مواجه می‌شوید، 🔸 و یک طراحی مفهومی قابل اجرا ایجاد می‌کنید. در این مرحله نیازی به تجربه و تسلط نیست. آموزش و رشد در دسترس اس…

21 Feb 2026, 07:49 UTC968 viewsread 6 August 2026
Video

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

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

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

“YazdBlueCup” (@YazdBlueCup), 657 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/YazdBlueCup.

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.