Channel
@qa_valencia
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
127subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002476393005 |
|---|---|
| Type | Channel |
| Username | @qa_valencia |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/qa_valencia |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 20:37 | 127 | -1 |
| 6 Sept 2026, 14:40 | 128 | +1 |
| 22 Aug 2026, 10:23 | 127 | -1 |
| 9 Aug 2026, 01:46 | 128 | no change |
| 7 Aug 2026, 23:08 | 128 | first reading |
13 posts held, back to 1 May 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 13 posts for this entry, the most recent from 18 June 2026. An engagement rate over an empty window would be a number about nothing.
90 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 32.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 29 | 32.2% | |
| 🔥 | 29 | 32.2% | |
| ❤ | 22 | 24.4% | |
| ❤🔥 | 5 | 5.56% | |
| 👏 | 3 | 3.33% | |
| 🤝 | 2 | 2.22% |
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 13 of the 13 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 90 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 1 May 2026 to 18 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.
Hi all, Thank you for coming and spending yesterday’s the morning with us. First of all, I would like to thank Ilia for his effort, presentation, and willingness to share his knowledge. And thank you all for the engaging discussion. I can clearly see how passionate and controversial the AI topic is. One way to reduce the heat around it is to keep talking about it, challenge our assumptions, and help each other ide…
🔥6❤3👏2
Good day everyone! Just a reminder about tomorrow’s QA breakfast! The last one till September! Register if you’re not and come if you have already done this! Take in mind that Floor changed. First floor instead of 6.
👍3
Hi everyone! 👋 The very last QA Breakfast of this season is happening on Wednesday, June 17 at 9:30 ☕️ 🎯 Topic: "Cheap to Build, Expensive to Get Right" We've all heard it by now: AI is making software cheap and fast to build. But once the demos and the hot takes are over, a more uncomfortable question is left on the table - if almost anyone can build almost anything, what is actually left for us to do? This w…
🔥10
I think yesterday we had a very active discussion and knew about each other something really special. I will try to add more such format events next season. Thank you all for participating! See you on our last QA Breakfast of this season 2 June 17. Save the date! It’s gonna be interesting.
❤13🤝2
Hi everyone 👋 The next QA Breakfast will take place on June 3 ☕ As we discussed it will be open discussion, sharing our stories and experiences without any specific topic. The main idea to get to know each other better and have a tasty breakfast. See you tomorrow at 9:30 (you can come earlier, I will be at the place around 9:15. 📍 Location: FIVEO BAR (https://share.google/4zfrwHs5TDpXt5Tnc) 🗓 Date: June 3 ⏰ Time:…
👍7
Hi everyone, There are 2 breakfasts left in this season of QA Breakfast. I’d like to give us a chance to truly get to know each other, since we all have quite different experiences and areas of expertise. So, I’d like to suggest spending our next event in the café (June 3) introducing ourselves and asking each other questions about our experience in different areas. I’ll moderate the meeting :) Please share if th…
👍9
Hi all, As an informational partner, I’d like to remind you about a local tech event happening this weekend. VLC Tech Fest is an open event for tech professionals. No registration is required - just come and participate. It’s a great opportunity to network with the local community and meet inspiring speakers. More details: VLC Tech Fest website
🔥6
Hi everyone, Today we had a great morning together with Kirill and his extensive practical knowledge of performance engineering. A big thanks to Kirill for his presentation and the discussion, and thank you all for participating. You can find the presentation using this link: https://docs.google.com/presentation/d/17NTdFYBbwBExqZroCaVYsQOunFlu9VNcFHo8SsiGmmc/edit?usp=drivesdk Also, if you want to dive deeper into…
❤4❤🔥2👍2👏1
Good morning everyone! Just a friendly reminder that our QA breakfast will be tomorrow. Register if you haven’t done it yet and join us tomorrow.
👍3
Hi all, The next QA Breakfast is happening on Wednesday, May 20th at 9:30 AM. 🎯 Topic: “From Good Code” to Production Reality” In April’s QA Breakfast, we discussed the hidden layer of the system - the Linux kernel, its specifics, limitations, and non-obvious behavior. This time, we’ll continue the topic from the application side. Even well-designed code can behave very differently in production. A service may loo…
🔥3
Today we had a cozy breakfast with an interesting discussion. Thank you guys for your participation! See you in two weeks at Ringcentral office!
🔥4❤🔥3❤2
Hi everyone 👋 The next QA Breakfast will take place on May 6 ☕ This time, we’ll dive into AI analysis in performance testing. My colleague Arseny Startsev, Senior Performance Engineer at RingCentral will share how we implemented AI analysis into our performance pipeline — and reduced testing effort by 2x. What you’ll learn: - How AI analysis helps in performance testing - What you need to make AI work for your goa…
👍3
Showing the 12 most recent of 13 posts we hold for @qa_valencia. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“QA breakfast in Valencia” (@qa_valencia), 127 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/qa_valencia.
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.