Channel
@productpeoplearmenia
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
150subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001857312154 |
|---|---|
| Type | Channel |
| Username | @productpeoplearmenia |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/productpeoplearmenia |
Technology — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 16 Sept 2026, 16:42 | 150 | +1 |
| 9 Sept 2026, 00:39 | 149 | +1 |
| 31 Aug 2026, 13:26 | 148 | +3 |
| 23 Aug 2026, 20:54 | 145 | +3 |
| 16 Aug 2026, 15:03 | 142 | +5 |
| 8 Aug 2026, 23:16 | 137 | no change |
| 7 Aug 2026, 14:49 | 137 | first reading |
12 posts held, back to 29 April 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 12 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
54 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 53.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 29 | 53.7% | |
| 🔥 | 24 | 44.4% | |
| 🥰 | 1 | 1.85% |
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 10 of the 12 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 54 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 29 April 2026 to 3 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.
📣 Upcoming Meetup: The New Rules of Product: Building with AI and Designing for Agents Product People is gathering again on August 13 at Yandex Hall. We have prepared an evening focused on how AI is radically transforming product management workflows and shifting user behavior. Agenda: 18:30 — Guests' arrival 19:00 — Vardan Dabaghyan: Product Management Transformation in the AI Era 19:30 — Narek Tamoyan: When AI Ag…
❤8
Hey folks 👋 We've finally locked in our next big one — meet Vibe Code Yerevan Hackathon. And it's less "competition", more a dedicated day to actually build the thing. You know that idea you've described to friends a hundred times but never had the time to make? This is the time. Blocked, focused, and with mentors sitting beside you the whole way from raw idea to a released product you can share. Join and ship you…
🔥7
Join us at Back to Back — a new backend conference built by engineers, for engineers ✨ Latency is creeping up, bottlenecks appear where you least expect them, and the architectural choices made a year ago are already haunting you today. Sound familiar? That’s exactly what Back to Back is about. In Yerevan, the main track will be "Architecture & Performance," dedicated to system efficiency, architectural patterns, a…
❤3
Yandex Armenia Startup Accelerator-ի գրանցումը բաց է 📷 Սա ձեր հնարավորությունն է՝ ձեր tech կամ IT նախագծի գաղափարը հասցնել հաջորդ մակարդակ։ Yandex Armenia-ի Startup Accelerator-ի դռները բաց են ուսանողական թիմերի, հետազոտական խմբերի և սկզբնական փուլում գտնվող ստարտափների համար։ Ծրագրի ընթացքում ձեր թիմը կաշխատի մեր ընկերության առաջատար փորձագետների, ինչպես նաև միջազգային խոշոր աքսելերատորներից հրավիրված խորհրդատուներ…
❤1
What will you gain from the Yandex Armenia internship? ✏️ Real Big Tech experience. No sandbox simulations or training tasks—you will ship projects that impact millions of users. Backend interns engineer high-load systems and build the next stage of Yandex Go services. Swipe through the cards for track details, selection stages, and terms. Apply now via the link: 📌 ➿➿➿ Ի՞նչ կստանանք Yandex Armenia-ի ինթերնշիփի …
❤4
What does it really take to build successful products in today’s market? ✏️ On May 14, we gathered at Yandex Hall to find out. Our speakers dropped some major insights: ✨ Anton Zhvakin highlighted that while the Product Manager title remains the same, the core expectations, required skill sets, and day-to-day realities of the role have fundamentally changed. ✨ Roman Krasilnikov shared insights into building a star…
🔥7❤1
Claude Code Live Workshop This session, we open up Claude Code and show what makes it different from a normal AI chatbot. ✅ Project understanding — see how Claude Code explores a real codebase and explains how everything works ✅ Live feature build — watch it plan, edit files, run checks, and fix issues in a real project ✅ Subagents — see how specialized AI agents can review code and handle focused tasks separately …
Tomorrow is the day! Product People is meeting at Yandex Hall to discuss the new PM reality and corporate startups. Doors open at 6:30. Anton Zhvakin and Roman Krasilnikov will share their cases, followed by an hour of quality networking. Registration closes soon. Get your ticket here
❤4
📣 Upcoming Meetup: The 2026 Playbook: How PMs and Corporations are Hacking Growth Product People is gathering again on May 14 at Yandex Hall. We have prepared an evening focused on the new realities of product management and corporate spin-offs. Agenda: 18:30 — Guests' arrival 19:00 — Anton Zhvakin: PM in 2026 - Same title. Different job. Sorry 19:30 — Roman Krasilnikov: Transport in Motion: How to Build a Startup …
❤8🔥2🥰1
🎉 CLAUDE CODE INTENSIVE 🗓 Flexible Dates 📍 AI9 Startup Campus Beginner to Master in 3 sessions (3h each) Claude Code isn’t ChatGPT. It reads your codebase, edits files, runs tests, connects to your tools, and executes workflows through AI agents. In 3 hands-on sessions, you’ll go from setup to building and running your own multi-agent system — on a real project, with a live demo at the end. What you’ll build: → P…
🔥5
We are LIVE NOW breaking down the Power-Interest Matrix. Learn exactly who can scale your product (Drivers) and who can kill it (Blockers). Jump in the stream before it ends and grab the free Miro template. Join us: https://us06web.zoom.us/j/81413869037
Already started the webinar that could change your career 🤩 Join us: https://us06web.zoom.us/j/81413869037
🔥3
Showing the 12 most recent of 12 posts we hold for @productpeoplearmenia. 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Product People Armenia” (@productpeoplearmenia), 150 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/productpeoplearmenia.
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.