Channel
@sedayetaybad
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,688subscribers
-5 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001000078989 |
|---|---|
| Type | Channel |
| Username | @sedayetaybad |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/sedayetaybad |
Local community — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 19 Sept 2026, 14:00 | 1,688 | -1 |
| 15 Sept 2026, 10:01 | 1,689 | -1 |
| 11 Sept 2026, 22:20 | 1,690 | +1 |
| 7 Sept 2026, 03:40 | 1,689 | +3 |
| 2 Sept 2026, 02:22 | 1,686 | -3 |
| 27 Aug 2026, 06:52 | 1,689 | +1 |
| 24 Aug 2026, 12:29 | 1,688 | -3 |
| 20 Aug 2026, 18:16 | 1,691 | -3 |
| 15 Aug 2026, 02:35 | 1,694 | -1 |
| 9 Aug 2026, 01:21 | 1,695 | +1 |
| 6 Aug 2026, 07:16 | 1,694 | no change |
| 6 Aug 2026, 02:21 | 1,694 | +1 |
| 5 Aug 2026, 18:47 | 1,693 | first reading |
13 posts held, back to 6 August 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 pages 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 13 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
با تلاوت آیاتی از کلام الله مجید قرار شبانه مردم شریف تایباد در میدان وحدت آغاز شد صدای تایباد صدای رسای هر شهروند تلگرام https://t.me/sedayetaybad ایتا https://eitaa.com/sedaye_taybad روبیکا @sedayetaybad
پیام تبریک مهندس محمود نعمتی، شهردار شهر کاریز، به مناسبت روز خبرنگار و سالروز شهادت شهید محمود صارمی ✍روابط عمومی شهرداری و شورای اسلامی شهر کاریز صدای تایباد صدای رسای هر شهروند تلگرام https://t.me/sedayetaybad ایتا https://eitaa.com/sedaye_taybad روبیکا @sedayetaybad
💢 پیام تبریک فرمانده انتظامی شهرستان تایباد به مناسبت روز خبرنگار خبرنگاران؛ روایتگران حقیقت و همراهان صادق پلیس در مسیر آگاهی و امنیت بسمالله الرحمن الرحیم هفدهم مردادماه، روز خبرنگار، فرصتی ارزشمند برای قدردانی از تلاشهای صادقانه خبرنگارانی است که با قلم و نگاه مسئولانه خود، در مسیر آگاهیبخشی، امیدآفرینی و خدمت به جامعه گام برمیدارند. خبرنگاران با انعکاس دقیق و منصفانه رویدادها، نقشی مهم در ا…
به نام خدا «ن وَالْقَلَمِ وَمَا یَسْطُرُونَ» ۱۷ مردادماه، روز خبرنگار، یادآور عهد و پیمان صادقانه اهالی قلم با حقیقت و آگاهی است؛ روزی برای پاسداشت دیدهبانان بیداری که با تعهد، انصاف و شجاعت، روایتگر رویدادها هستند. امسال در حالی به استقبال این روز میرویم که فضای کشور و دلهایمان با عطر شهادت و فرهنگ ایثار عجین شده است؛ یاد و خاطره شهید والامقام «محمود صارمی» و تمامی شهدای عرصه خبر و رسانه را گرامی میداریم و بر …
بسم الله الرحمن الرحیم «إِنَّا لِلَّهِ وَإِنَّا إِلَیْهِ رَاجِعُونَ» جناب آقایان یاور و خالد جامی، خانوادههای معظم و محترم جامی، محمدپرست و جامعه محترم ورزش با نهایت تأسف و تأثر، درگذشت مرحوم مغفور حاج ابراهیم جامی را صمیمانه به محضر شما خاندان محترم و سایر بازماندگان معزز تسلیت و تعزیت عرض مینماییم. بیتردید فقدان این بزرگوار، اندوهی سنگین برای خانواده، خویشاوندان و دوستان ایشان است. از درگاه خداوند متعال برا…
انا لله و انا الیه راجعون خانواده ارجمند جامی از شنیدن خبر درگذشت حامی و ورزشکار خوشقلب و دوستداشتنی آقای ابراهیم جامی عمیقاً ناراحت و متأسف شدیم. درگذشت این عزیز از دست رفته را به شما وخانواده مکرّم و گرامی ایشان، تسلیت میگویم. از خداوند متعال برای زنده یاد خواهان رحمت واسعۀ الهی را دارم. غلام حضرت پیله ور صدای تایباد صدای رسای هر شهروند تلگرام https://t.me/sedayetaybad ایتا https://eitaa.com/sedaye_taybad رو…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
پنجشنبه است سکوت😒 گورستان را میشنوی؟ دنیا ارزش💔 دل شکستن ندارد میرسد روزی💌 که هرگز در دسترس نخواهم بود🖤 خاک آنتن نمیدهد با فاتحه یادی کنیم از عزیزان سفرکرده🩶 صدای تایباد صدای رسای هر شهروند تلگرام https://t.me/sedayetaybad ایتا https://eitaa.com/sedaye_taybad روبیکا @sedayetaybad
هر روز صبح ساعت هشت و نیم سلام، پنجشنبه به یاد درگذشتگان 🔸صدای تایباد، صدای رسای هر شهروند https://t.me/sedayetaybad
Photo, posted without a caption
Showing the 12 most recent of 13 posts we hold for @sedayetaybad. 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 5 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“صدای تایباد” (@sedayetaybad), 1,688 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/sedayetaybad.
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.