Telegram RegisterThe public register of Telegram
Telegram profile photo for اخبار بازنشستگان شهرداری تهران

Channel

اخبار بازنشستگان شهرداری تهران

@bazneshastegi

On this record: Observations · Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry

5,200subscribers

+16 since we began measuring on 29 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001002468712
TypeChannel
Username@bazneshastegi
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live5 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/bazneshastegi

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.

Views per post sit far above this size band

4,990 average views per post against 5,200 subscribers — an engagement rate of 95.9%. Across the 5,231 registered channels in the same cohort — 3,163–9,999 subscribers, posting mainly in Persian — the middle half sit between 4.20% and 18.0%, with a median of 9.24%.

What this was computed from
Window30 days (10 August 2026 9 September 2026)
Posts measured14 of 14 published in the window (0 exact, 14 rounded by Telegram)
Views totalled69,820
Mature posts only100.5% over 13 posts read at least 24h after publication
Subscribers5,200 measured 5 September 2026
Cohortb3162:fas · 5,231 channels · p10 1.82% · p25 4.20% · p50 9.24% · p75 18.0% · p90 30.0%
Position in cohort99.369th percentile · 10.4× the cohort median
Uncertainty±0.058% of the figure, from Telegram’s rounding
Post languagePersian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 9 September 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.

Growth

5,1845,2005,19229 August 2026 — 5,184 subscribers29 August 2026 — 5,185 subscribers1 September 2026 — 5,192 subscribers5 September 2026 — 5,200 subscribers29 August 20265 September 2026
4 measurements spanning 7 days, net +16. 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 5,182–5,202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 00:185,200+8
1 Sept 2026, 16:135,192+7
29 Aug 2026, 16:195,185+1
29 Aug 2026, 06:155,184first reading

Engagement

20 posts held, back to 25 July 2026the 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.

ERR · 30 days
95.9%
avg views ÷ 5,200 subscribers
Avg views / post
4,990
14 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
14
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held20 (25 July 202628 August 2026)
Views total69,820
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 06:15 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.

What this channel posts

Video runtime
1m 14s
Average length
1m 14s

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.

Recent posts

28 Aug 2026, 08:47 UTC≈1,890 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. جمعه ۶ شهریور : کرج و بخشی از منطقه ۲۲ شهر تهران یکشنبه ۸ شهریور: منطقه ۲۲ شهر تهران @bazneshastegi

26 Aug 2026, 08:27 UTC≈2,280 viewsread 29 August 2026
Photo

بهره‌مندی کارکنان و بازنشستگان شهرداری تهران از تخفیف رستوران عمارت میعاد 🔸به گزارش روابط عمومی اداره‌کل رفاه، تعاون و خدمات اجتماعی شهرداری تهران، در راستای توسعه و ارتقای عادلانه خدمات رفاهی برای خانواده بزرگ شهرداری تهران، امکان استفاده از تخفیف ویژه در رستوران «عمارت میعاد» فراهم شده است. 🔹کارکنان و بازنشستگان محترم شهرداری تهران می‌توانند با ارائه کارت جامع خدمات رفاهی یا کارت شناسایی شهرداری تهران، به‌همراه خ

26 Aug 2026, 05:09 UTC≈2,540 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. چهارشنبه ۴ شهریور: منطقه ۲ و بخشی از منطقه ۵ شهر تهران پنجشنبه ۵ شهریور: منطقه ۵ و بخشی از منطقه ۲۲ شهر تهران @bazneshastegi

23 Aug 2026, 13:08 UTC≈4,160 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. دوشنبه ۲ شهریور : مناطق ۱ و ۳ و حومه شرق و بخشی از منطقه ۲ شهر تهران سه شنبه ۳ شهریور : بخشی از منطقه ۲ شهر تهران @bazneshastegi

21 Aug 2026, 22:46 UTC≈5,210 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. یکشنبه ۱ شهریور: منطفه ۴ و بخشی از منطقه ۱ شهر تهران @bazneshastegi

19 Aug 2026, 20:23 UTC≈6,140 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. پنج شنبه ۲۹ مرداد : مناطق : ۱۳-۸ و بخشی از منطقه ۴ شهر تهران جمعه ۳۰ مرداد : مناطق : ۶-۷-۱۱-۱۲ و بخشی از منطقه ۴ شهر تهران @bazneshastegi

17 Aug 2026, 17:39 UTC≈6,650 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. چهارشنبه ۲۸ مرداد مناطق ۲۰-۱۹-۱۶-۱۵-۱۴ و بخشی از منطقه ۱۳ شهر تهران @bazneshastegi

16 Aug 2026, 16:41 UTC≈7,270 viewsread 29 August 2026

‍ ‍🔴بازنشستگان و موظفین محترم شهرداری تهران با سلام به اطلاع می رساند سبد پروتئین فصل تابستان سال ۱۴۰۵ با برنامه ریزی های انجام شده در مرحله توزیع می باشد. لذا چون دوره های گذشته لطفا به نکات ذیل توجه فرمایید: ✅ دومین سبد سال ۱۴۰۵شامل ۱۴ کیلوگرم گوشت قرمز و مرغ به شرح ذیل می باشد: ۱-ران و سردست گوسفندی یک بسته ۲۰۰۰ گرمی ۲-ران گوساله یک بسته ۲۰۰۰ گرمی و یک بسته ۱۰۰۰ گرمی ۳-ران مرغ بی پوست سه بسته ۱۸۰۰ گرمی ۴-سینه م

16 Aug 2026, 16:39 UTC≈6,020 viewsread 29 August 2026

توزیع دومین سبد پروتئین سال ۱۴۰۵ بازنشستگان شهرداری تهران به شرح ذیل می باشد. سه شنبه ۲۷ مرداد مناطق ۲۱-۱۸-۱۷-۱۰-۹ شهر تهران @bazneshastegi

16 Aug 2026, 16:37 UTC≈5,380 viewsread 29 August 2026

‍ ‍ معاون امور بازنشستگان‌ و مشترکین خبرداد: آغاز توزیع سبد کالای پروتئین فصل تابستان از روز سه شنبه معاون امور بازنشستگان‌ و مشترکین از توزیع سبدکالا در روز سه‌شنبه (بیست و هفتم مرداد ماه) خبرداد. به گزارش روابط عمومی سازمان بازنشستگی شهرداری تهران، حمیدرضا خادمی؛ معاون امور بازنشستگان‌ و مشترکین از آغاز توزیع دومین سبد کالا پروتئین در سال جاری (ویژه فصل تابستان) و ارسال به درب منازل بیش از ۹ هزار بازنشسته و موظف

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

Appears in Telegram’s recommendations for other channels

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.

شهردارچي
@Shahrdarchi · 42,263
Telegram ranks this channel #24 of 85 here — alongside 84 others — read 29 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“اخبار بازنشستگان شهرداری تهران” (@bazneshastegi), 5,200 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/bazneshastegi.

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.