Channel
@pyerevan
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
833subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001214464233 |
|---|---|
| Type | Channel |
| Username | @pyerevan |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/pyerevan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 14:13 | 833 | +1 |
| 22 Aug 2026, 20:36 | 832 | +2 |
| 8 Aug 2026, 01:30 | 830 | no change |
| 7 Aug 2026, 23:08 | 830 | first reading |
20 posts held, back to 29 January 2025 — 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 13 June 2026. An engagement rate over an empty window would be a number about nothing.
139 reactions across 19 posts, in 10 distinct kinds. The most used accounts for 46.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 65 | 46.8% | |
| 🔥 | 23 | 16.5% | |
| 👍 | 22 | 15.8% | |
| ❤🔥 | 9 | 6.47% | |
| 🤨 | 9 | 6.47% | |
| 😁 | 5 | 3.60% | |
| 🏆 | 2 | 1.44% | |
| 👏 | 2 | 1.44% | |
| 🍓 | 1 | 0.719% | |
| 🥰 | 1 | 0.719% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 139reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 January 2025 to 13 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔥 TICKETS ARE LIVE! PyData & PyCon Yerevan 2026 is happening on July 24–25, and we'd love to see you there. 🎟️ Grab your ticket now: https://eventhub.am/am/other/event/pydata-pycon-yerevan-2026-88ac846d-98d1-484b-9779-7405835da7c1 Don't wait. Get in. -- #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
🔥3
Dear community, as the Zen of Python tells us: Now is better than never. It is better to have a talk proposal than a 'TODO' in your brain. Submit yours today at pycon.am! 🐍🇦🇲
😁5❤1
📢 𝗧𝗵𝗲 𝗖𝗮𝗹𝗹 𝗙𝗼𝗿 Proposals is now 𝗢𝗣𝗘𝗡! From now on 𝗣𝘆𝗗𝗮𝘁𝗮 𝗣𝘆𝗖𝗼𝗻 𝗬𝗲𝗿𝗲𝘃𝗮𝗻 𝟮𝟬𝟮𝟲 is accepting talk proposals. 📍 Submit your talk at https://pycon.am/ ⏳Submission deadline: April 19, 2026 This conference brings together Python, data, and research communities in one place – across industries, backgrounds, and experience levels. We welcome practical case studies, research presentations, technical deep-dives, lessons fro…
❤4🏆2
📢 PyData & PyCon are coming together This is happening! 📍 Yerevan 📅 July 24 - 25, 2026 Now in its second edition, PyData & PyCon Yerevan 2026 brings PyData and PyCon together to gather the local and global data, research, and Python community in Yerevan. Led by the American University of Armenia and the Akian College of Science & Engineering, the conference creates a shared space for learning, exchange, and colla…
🔥3❤🔥2
Hello there dear fellow community members :) Join the organizers of the PYerevan community as we reveal the "secrets" behind building a sustainable and trusted tech community over the past seven years. From managing a non-profit to organizing successful meetups, finding sponsors, and securing speakers, we'll share their hands-on experience. we'll also discuss how the Python landscape in Armenia has evolved, providin…
❤9🔥5👍1👏1
Today’s the day! 🎉 See you in a couple of hours! There’s still time to grab your spot for an inspiring talk with Eric Meadows. 🎟 Register now: lu.ma/zicamg17 📍 AI9 Startup Campus, 9 Isahakyan St. 🕖 19:00 — We’ll be waiting for you!
⏳ Last Call! Only 3 days left until the PyData Yerevan Open Source Sprint - and registration closes in just a few hours! 📅 Sprint Date: August 15 🕒 Registration closes: August 13 (END OF THE DAY) 📍 Location: American University of Armenia This is your final chance to: ✅ Learn how to contribute to pandas with hands-on mentoring ✅ Make your first open-source pull request ✅ Work alongside experienced developers an…
👍1
🚀 PYerevan Meetup – This Wednesday! 🐍 Hey Pythonistas, the wait is almost over! 🎉 Join us on Wednesday, August 13 at 19:00 at AI9 Startup Campus for an inspiring session with Eric Meadows (Co-founder & CTO, Sailfish AI). 🎟 Save your spot: lu.ma/zicamg17 Can’t wait to see you there! 😍
❤2🥰1
https://t.me/pyerevan
🤨9🍓1
Hey dear Pythonistas! 🥳 Reserve your calendars for August 13th and bring a friend — it’s time for another exciting PYerevan meetup! This time, we’re hosting one brilliant speaker: Eric Meadows, Co-founder and CTO of Sailfish AI, will present how they got off GitHub actions to stabilize build process. You will learn how they leveraged Argo Workflows to handle their CI processes. Previously, Eric also created the w…
👍3❤2
Dear Pythonistas! See you today on 19:00 at PMI Science R&D Center 🐍 Dropping a map point here, Just in case you don't know how to get there. And, please do not forget to register!
❤🔥4👍2🔥1
Hello, dear Python community members! We hope you are having a wonderful day off and celebrating Republic Day! 🎉 🎇 We are excited to meet you on Friday at PMI Science R&D Center 😃 Please do not forget to register! Registration is mandatory, and it will save you time at the entrance and will help us to plan the event better. Register here!
❤4❤🔥3👍1🔥1
Showing the 12 most recent of 20 posts we hold for @pyerevan. 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“PYerevan” (@pyerevan), 833 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/pyerevan.
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.