Channel
@pydatayerevan
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
466subscribers
-4 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001960721954 |
|---|---|
| Type | Channel |
| Username | @pydatayerevan |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/pydatayerevan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 23:18 | 466 | -2 |
| 1 Sept 2026, 06:13 | 468 | +3 |
| 25 Aug 2026, 03:04 | 465 | -2 |
| 17 Aug 2026, 11:05 | 467 | -3 |
| 8 Aug 2026, 04:46 | 470 | no change |
| 8 Aug 2026, 01:31 | 470 | first reading |
20 posts held, back to 23 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 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
83 reactions across 15 posts, in 4 distinct kinds. The most used accounts for 69.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 58 | 69.9% | |
| 🔥 | 16 | 19.3% | |
| 🤩 | 5 | 6.02% | |
| 👍 | 4 | 4.82% |
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 16 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 83 reactions 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 23 July 2026 to 7 August 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.
🙌 A little post-conference thank you goes to Intelinair! By purchasing a Corporate Ticket for PyData & PyCon Yerevan 2026, IntelinAir chose to support the conference and everything that came with it. We truly appreciate having you among our supporters. #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
❤2
🙌 Some support deserves a special mention. A big thank you to Mayflower for supporting PyData & PyCon Yerevan 2026 through a Corporate Ticket. It means a lot to have companies that choose to support the community and what we are building together. Thank you for being part of it! #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
❤4
📸 The memories are waiting. The official photos from PyData & PyCon Yerevan 2026 are now ready. See if you can find yourself, your friends, or your favorite conference moment. 🔗 Photos: https://drive.google.com/drive/folders/1Q42Gw1qwvhwC3otg8HCs8PvpYMgWmBae #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
🤩3❤2🔥2
🔷 Some conversations at PyData & PyCon Yerevan 2026 might just lead to your next career move. Our Diamond Sponsor, VXSoft LLC, is hiring! Current openings: • Support Center Specialist - https://vxsoft.com/en/support_specialist • Application Security Engineer / Penetration Tester - https://vxsoft.com/en/penetration_tester • Project Manager - https://vxsoft.com/en/job/project_manager If one of these sounds like t…
❤2🔥1
🔷 What's next after PyData & PyCon Yerevan 2026? Maybe... your next job. Our Platinum Sponsor, WorldQuant, is looking for talented people to join their team in Yerevan. Open roles: • Senior Python Engineer – AI/ML Systems • Lead Python Engineer – AI/ML Systems • AI Software Developer • Quantitative Researcher Take a look and see if one of them is the right fit for you! 🔗 Apply here: https://www.worldquant.com/ca…
❤4👍3🔥3
🎉 The conference may have lasted two days. Building it took much longer. Meet Mane Vardanyan, one of the organizers behind PyData & PyCon Yerevan 2026. #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
❤7🤩2
🎉 The stage is empty. The story behind it is worth telling. Meet Karen Javadyan, one of the organizers behind PyData & PyCon Yerevan 2026. #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
❤5🔥2
🎉 Some conferences end when the lights go off. The best ones continue through the ideas, conversations, and connections they leave behind. Meet Suren Poghosyan, one of the organizers behind PyData & PyCon Yerevan 2026. #pydatapycon2026 #pydatayerevan #pyerevan #pycon2026 #python #ML #AI #computervision #techevents #conference #AUA #ACSE
🔥6❤5
😃 Gooood morning Yerevan ! We were glad to host you at the PyData & PyCon Yerevan 2026 and would be even happier to see you posting the highlights from the conference and tagging us. 🖼️ We are collecting a library of moments from the point of view of our attendees and will put it in our website. You also can send your moments to [email protected] with a short text message that will be added at the bottom of the p…
❤9
PyData Yerevan pinned «Don't miss the AFTER PARTY! Location - AI9 Time - 19:00»
Don't miss the AFTER PARTY! Location - AI9 Time - 19:00
❤1
Welcome to day 2 ! After the registration please proceed to Manoogian Hall, we will start at 9:45AM.
Showing the 12 most recent of 20 posts we hold for @pydatayerevan. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“PyData Yerevan” (@pydatayerevan), 466 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/pydatayerevan.
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.