Channel
@boukanshora6
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
673subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001250877141 |
|---|---|
| Type | Channel |
| Username | @boukanshora6 |
| Description | اخبار فعالیت های ششمین دوره شورای اسلامی شهر بوکان ارتباط با ما : @Sh6bo |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/boukanshora6 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 21:00 | 673 | no change |
| 8 Aug 2026, 20:47 | 673 | first reading |
9 posts held, back to 30 July 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 9 (30 July 2026 – 7 August 2026) |
| Views total | 2,339 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 21:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
پیام تبریک رئیس و اعضای شورای اسلامی شهر بوکان به مناسبت «روز خبرنگار» به نام خداوند لوح و قلم هفدهم مرداد، فرصتی است برای تجلی ارادت به ساحت کسانی که رسالتشان، تعهد به حقیقت و آرمانشان، روشنگری مسیر جامعه است. این روز، که با نام شریف شهید مزارشریف، شهید عرصهی خبر «محمود صارمی» گره خورده است، یادآور آن است که خبرنگاری نه یک پیشه، که یک رزم بیتوقف در میدان آگاهیبخشی است. شهید صارمی، با نثار خون خویش، معنای حقیقی…
🔰شهردار در میان مردم حضور مدیران شهری در مسجد النبی(ص) ◾️به گزارش روابط عمومی شهرداری بوکان؛ روز گذشته معاون سیاسی امنیتی فرمانداری، معاون هماهنگ کننده سپاه پاسداران بهمراه علی قادری رئیس شورای اسلامی شهر و امیر احمـدی شهردار بوکان، قسمتی معاون عمرانی شهرداری و جمعی از مدیران و کارشناسان ادارات خدمات رسان شهرستان در مسجد البنی (ص) این شهر حضور پیدا کرده و با ساکنین و اهالی کوچه فرامرزی و خیابان مام صاحبی دیدار و گفت…
🔵برگزاری جلسه کمیته حملونقل دانشآموزی شهرستان بوکان 🔶روز یکشنبه ۱۱ مرداد ماه ۱۴۰۵ جلسه کمیته حملونقل دانشآموزی شهرستان بوکان با حضور رئیس و اعضای شورای اسلامی شهر، معاون برنامهریزی و هماهنگی امور عمرانی فرمانداری، جانشین پلیس راهور، رئیس سازمان حملونقل شهرداری، نمایندگان اداره تعزیرات حکومتی، صنعت، معدن و تجارت (صمت)، آموزش و پرورش، انجمن اولیا و مربیان و مدیران شرکتهای حملونقل دانشآموزی برگزار شد. 🔸در این…
Photo, posted without a caption
◾️فرا رسیدن اربعین سرور و سالار شهیدان امام حسین(ع) بر عموم مسلمین جهان تسلیت باد. @boukanshora6
🔵بازدید مسئولین شهرستان بوکان به منظور ساماندهی زیرساختهای شهرک مسکن ملی کوی بهداری 🔶امروز یکشنبه ۱۱ مردادماه ۱۴۰۵ در راستای بررسی و رفع دغدغههای زیرساختی ساکنان مسکن ملی کوی بهداری، مهندس صنعتی فرماندار شهرستان بوکان به همراه حاج کمال کریمی عضو شورای اسلامی شهر، امیر احمدی شهردار بوکان، محمدپور معاون برنامهریزی و هماهنگی امور عمرانی فرمانداری و همچنین امجدی معاون بهرهبرداری شرکت آب و فاضلاب آذربایجانغربی و رؤس…
✳️جوابیه شهرداری بوکان در خصوص دلیل تاخیر در انتشار نقشه آخرین محدوده مصوب طرح جامع تجدید نظر شهر بوکان ابلاغی ۱۴۰۵/۰۲/۱۹ : ◾️به استحضار عموم شهروندان ارجمند می رساند: با عنایت به اینکه طرح جامع تجدید نظر بوکان بعد از انجام مطالعات توسط مشاور طرح در نشست مورخه ۱۴۰۴/۰۹/۰۱ شورای برنامه ریزی و توسعه استان آذربایجان غربی تصویب و در نشست مورخه ۱۴۰۵/۰۱/۳۱ شورایعالی شهرسازی و معماری ایران تصویب و در مورخه ۱۴۰۵/۰۲/۱۹ مصوب…
🔳جناب آقای علی قادری رییس محترم شورای اسلامی شهر مصیبت وارده را خدمت شما عزیزان و خانواده محترم تسلیت عرض کرده برای آنمرحومه علو درجات الهی و برای بازماندگان صبر جمیل را از درگاه خداوند متعال خواستاریم. روابط عمومی شورای اسلامی شهر و شهرداری بوکان
🔵برگزاری نشست بررسی و تکمیل طرح جامع توسعه شهری بوکان 🔶روز چهارشنبه ۷ مردادماه ۱۴۰۵ جلسه بررسی طرح جامع شهر بوکان با محوریت سیاستهای پیشنهادی توسعه شهری و شناسایی و جمعبندی طرحها و پروژههای سرمایهگذاری، با حضور فرماندار شهرستان بوکان، نماینده مردم فهیم بوکان در مجلس شورای اسلامی، دادستان و رئیس دادگستری، فرمانده نیروی انتظامی، رئیس و اعضای شورای اسلامی شهر، شهردار بوکان و معاونت شهرسازی، رئیس اداره راه و شهرساز…
Showing the 9 most recent of 9 posts we hold for @boukanshora6. 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.
Citation-graph rank — 850,708 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“شورای اسلامی شهر بوکان” (@boukanshora6), 673 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/boukanshora6.
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.