Channel
@qazvin_rcs
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,139subscribers
-13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001066642993 |
|---|---|
| Type | Channel |
| Username | @qazvin_rcs |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/qazvin_rcs |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 18 Sept 2026, 18:58 | 1,139 | -3 |
| 14 Sept 2026, 07:37 | 1,142 | -1 |
| 5 Sept 2026, 20:18 | 1,143 | -5 |
| 1 Sept 2026, 14:55 | 1,148 | +1 |
| 29 Aug 2026, 13:54 | 1,147 | +1 |
| 26 Aug 2026, 19:13 | 1,146 | +2 |
| 16 Aug 2026, 15:58 | 1,144 | -1 |
| 12 Aug 2026, 20:23 | 1,145 | -5 |
| 9 Aug 2026, 23:31 | 1,150 | -1 |
| 7 Aug 2026, 03:23 | 1,151 | -1 |
| 6 Aug 2026, 09:06 | 1,152 | no change |
| 6 Aug 2026, 08:47 | 1,152 | first reading |
3 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 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 3 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
📸 #گزارش_تصویری۸ | پایان مأموریت درمانگاه «الاقمار» پس از ۱۴ روز خدمترسانی شبانهروزی به زائران اربعین حسینی، روند جمعآوری تجهیزات و پایان فعالیت درمانگاه الاقمار توسط تیم اعزامی جمعیت هلالاحمر استان قزوین انجام شد. این مأموریت با تلاش شبانهروزی کادر درمان، نیروهای پشتیبانی و داوطلبان به پایان رسید و برگ زرین دیگری از خدمت صادقانه هلالاحمر در مسیر زائران حضرت اباعبدالله الحسین (ع) رقم خورد. @qazvin_rcs
⭕️ برگزاری جشنواره ورزشی کانونهای دانشجویی هلال احمر قزوین؛ احیای بازیهای بومی محلی در کانون داوطلبی مدیرعامل جمعیت هلال احمر استان قزوین گفت: به منظور ارتقای سطح تعاملات میان دانشجویان داوطلب و ایجاد بستری برای تقویت روحیه تیمی، مسابقات ورزشی ویژه کانونهای دانشجویی جمعیت هلال احمر استان با میزبانی شهرستان قزوین برگزار شد. 🔻به گزارش روابط عمومی جمعیت هلال احمر استان قزوین؛ حبیب درگاهی، با اشاره به اهمیت نقش دا…
Photo, posted without a caption
Showing the 3 most recent of 3 posts we hold for @qazvin_rcs. 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 6 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“جمعیت هلال احمر استان قزوین” (@qazvin_rcs), 1,139 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/qazvin_rcs.
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.