.

Channel
زنجیره تولید گوشت مرغ پیگیر
@paygirco
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
66subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001056299394 |
|---|---|
| Type | Channel |
| Username | @paygirco |
| Description | www.paygir.com |
| Created | Between 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/paygirco |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 02:01 | 66 | no change |
| 7 Aug 2026, 22:55 | 66 | first reading |
Engagement
20 posts held, back to 3 November 2019 — 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.
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 30 March 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 404
- Videos
- 4
- Links
- 20
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 1m 21s
- Average length
- 1m 21s
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
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 10 days, that account will self-destruct and this channel may no longer have an owner.
قابل توجه همکاران گرامی سامانه ارزیابی عملکرد کارکنان جهت دوره چهارم سال ۱۳۹۸ در روز پنجشنبه ۲۸ فروردین ماه ۹۹ باز گشایی گردید. واحد تحقیق و توسعه R&D @paygirco
خرید تضمینی مرغ برای جبران خسارت ناشی از کرونا ♦️کریمی گفت: با توجه به شیوع کرونا برای جلوگیری از زیان مرغداران گلستانی مرغ به قیمت تضمینی خریداری و در سردخانه ها ذخیره می شود. ♦️به گزارش خبرنگار خبرگزاری شبستان از گرگان، «ابراهیم کریمی» عصر امروز(یکشنبه 17 فروردین) در گفتگو با خبرنگاران اظهار کرد: کرونا همه موضوعات از جمله حوزه اقتصادی را تحت تأثیر قرار داده و تمام تلاش ما آن است که فشار وارده بر مردم به ویژه قشر …
قابل توجه همکاران گرامی سامانه ارزیابی عملکرد کارکنان جهت دوره چهارم سال ۱۳۹۸ به زودی باز گشایی می گردد. واحد تحقیق و توسعه R&D @paygirco
نوروز ۱۳۹۹ مبارک @paygirco
نحوه شستشوی صحیح دست ها @paygiruni
قابل توجه همکاران گرامی دوره سوم ارزیابی عملکرد کارکنان در سال ۹۸ به پایان رسید و حساب آینده همکاران نیز در راستای قدردانی از تلاش های کارکنان در تاریخ ۸ بهمن ماه شارژ گردید. پاینده باشید واحد تحقیق و توسعه @paygirco
گواهی کارگاه آموزشی بررسی عملیات جوجه کشی به منظور افزایش کمی و کیفی جوجه در مرغ مادر گوشتی با تدریس آقای دکتر سروش خادمیان آماده تحویل می باشد. لطفا جهت گرفتن گواهی شخصا به دفتر واحد تحقیق و توسعه واقع در مرکز آموزش علمی کاربردی شرکت پیگیر مراجعه نماید. با تشکر واحد تحقیق و توسعه R&D @paygirco
واحد تحقیق و توسعه برگزار می کند: کارگاه آموزشی مکمل سازی مدرسین: دکتر فرهاد فرودی و مهندس علی افسر محل برگزاری: تهران زمان: پنج شنبه ۱۷ بهمن ۹۸ R&D @paygirco
سمینار بیماری های متابولیسمی و تاثیر مواد معدنی بر آن دوشنبه ۳۰ دی ماه مرکز آموزش علمی- کاربردی شرکت پیگیر R&D @paygirco
قابل توجه همکاران گرامی سامانه ارزیابی عملکرد کارکنان جهت دوره سوم سال ۱۳۹۸ در ساعت ۲۴ امشب ۱۹ دی ماه باز گشایی می گردد. واحد تحقیق و توسعه R&D @paygirco
Showing the 12 most recent of 20 posts we hold for @paygirco. 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
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“زنجیره تولید گوشت مرغ پیگیر” (@paygirco), 66 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/paygirco.
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.