Channel
@GoogleDevSpaceSG
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,917subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001887969473 |
|---|---|
| Type | Channel |
| Username | @GoogleDevSpaceSG |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/GoogleDevSpaceSG |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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, 18:00 | 4,917 | -2 |
| 13 Sept 2026, 04:01 | 4,919 | -11 |
| 9 Sept 2026, 05:59 | 4,930 | -1 |
| 4 Sept 2026, 02:01 | 4,931 | +5 |
| 28 Aug 2026, 08:48 | 4,926 | +5 |
| 22 Aug 2026, 18:09 | 4,921 | +7 |
| 19 Aug 2026, 06:45 | 4,914 | +2 |
| 16 Aug 2026, 17:16 | 4,912 | +3 |
| 13 Aug 2026, 01:15 | 4,909 | +6 |
| 10 Aug 2026, 11:37 | 4,903 | +1 |
| 7 Aug 2026, 12:38 | 4,902 | +1 |
| 7 Aug 2026, 05:17 | 4,901 | first reading |
20 posts held, back to 13 October 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 8 pages 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.
144 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 73.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 106 | 73.6% | |
| 🔥 | 16 | 11.1% | |
| 👍 | 11 | 7.64% | |
| ⚡ | 7 | 4.86% | |
| 🐳 | 1 | 0.694% | |
| 👏 | 1 | 0.694% | |
| 💯 | 1 | 0.694% | |
| 🤩 | 1 | 0.694% |
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 17 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 144 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 13 October 2025 to 28 July 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 events at 📍Google Developer Space next week! Lorong AI - Building Tools for Your Business w/ Google AI Studio 📅 August 4th, 2026 (Tuesday) 🕗 7:00 PM to 9:00PM 📍 Lorong AI @ One North, Singapore 🔗 https://goo.gle/builder-aug-2026 🤝 Complete Beginners and Builders: Hands-on workshop featuring Google DeepMind for business use cases GDG Monthly Meetup: Building Next-Gen AI Agents 📅 August 4th, 2026 (Tuesday) 🕗…
❤5
Hey Builders! 🚀 We’re hosting Build with Gemini Singapore — an immersive hands-on experience. If you are a working professional, whether you code raw syntax or vibe coding with prompts, we've got a track for your skillset! 📅 Date: August 5 (Wed) ⏰ Time: 8:30 AM – 5:30 PM 📍 Venue: Marina Bay Sands Expo & Convention Level 4 The Experience: 🚀 Keynote & Interactive Demos 🛠 Hands-on Labs ⚡️ Lightning Talks 🧠 "Ask t…
❤14👍4🔥1
Have you heard enough about AI Agents yet? Join us for an evening of hands-on learning with Agent Development Kit. We’ll kick things off with a quick look at ADK 2.0, including the latest features and what’s changed, before diving into the real fun, agent memory. If you’ve ever wondered how to manage complex state or give your agents long-term memory that actually holds up, this session is for you. Come ready to a…
❤12
🚀 Google I/O Extended Singapore 2026 Missed the action from Mountain View? We’ve got you covered. Join us for an afternoon dedicated to the latest developer tools, platform updates, and open-source AI integrations across Web, Mobile, Flutter, Android, and Firebase. 🛠️ Full agenda is on the way, but registrations are live now. Pair it with the morning Cloud session for the ultimate developer Saturday! Event Details…
🔥4
🚀 Google Cloud Next Extended Singapore 2026 We’re bringing the biggest cloud and AI breakthroughs straight from Las Vegas to the local community. If you want to look under the hood of Agentic AI, enterprise data infrastructure, and next-gen cloud security, this is your spot. Agenda is dropping soon, but seats are strictly limited — lock in your Saturday morning plans early! Event Details: 📅 Date: Saturday, June 27…
❤4👍1
Next week is buzzing with community events featuring Googlers from DeepMind and Cloud! Check out the details below and mark your calendars: 🤖 Event 1: AI Engineer Gemini Event Join Machine Learning Singapore and Google DeepMind for an exciting evening of deep dives and lightning talks focused on building with Gemini. Come for the cutting-edge tech talks, and stay to connect with the local machine learning community!…
👍3❤2
🚀 GDG Monthly Meetup #2604: Supercharge Your Agents Ready to take your AI builds to the next level? This month, we’re moving beyond the prompt and diving into the world of autonomous action. Event Details: 📅 Date: Tuesday, April 28, 2026 ⏰ Time: 6:30 PM - 9:00 PM 📍 Venue: Google Developer Space, Singapore 🎟️ Register here: bit.ly/gdgsg-apr26 Whether you’re a seasoned dev or just AI-curious, come for the technical …
❤10
🚀 Ready to vibe-code the future? Join us for Build with AI Singapore 2026 on March 28! We're hosting a massive double-feature hands-on day: 🌅 AM: Vibe-Coding Breakfast (Architect to Orchestrator) 🌆 PM: The Gemini Deep Dive (Mastering the Engine) 💻 Bring your laptop and build with Gemini 3.1 & Agentic AI. Let's stop debugging the past and start orchestrating the future! 📍 Google Developer Space, SG 👇 Grab your spot…
❤12
Google DeepMind and Cerebral Valley: Gemini 3 Singapore Hackathon 📅 Date: Mar 7, 2026 (Saturday) 🕗 Time: 9:00 AM – 10:00 PM 🔗 Register now: https://cerebralvalley.ai/e/gemini-3-singapore-hackathon Prizes 🏆Gemini API Credits: $100,000 USD 🏆Exclusive 30-minute virtual call with the founders of Google's AI Future Fund
❤6🔥2👍1
Upcoming events at 📍Google Developer Space next week! Data Science SG - Building Reliable AI: From Knowledge Work to Data Agents 📅 February 24, 2026 (Tuesday) 🕗 6:30 PM to 8:30PM 📍 Google Developer Space, Singapore 🔗 https://bit.ly/dssg-feb-2026 GDG Monthly Meetup #2602: Vibe-Coding Evening 📅 February 25, 2026 (Wednesday) 🕗 6:30 PM to 9:00 PM 📍 Google Developer Space, Singapore 🔗 https://bit.ly/gdgsg-feb-2026 Mach…
❤7
🚀 GDG Monthly Meetup #2602: Vibe-Coding Evening The world of coding just changed. Again. Are you still wrestling with syntax while the "vibes" are passing you by? Join us for GDG Singapore’s Monthly Meetup #2602, a high-octane Build with AI session where we trade manual labor for pure creative intent. This is the Vibe-Coding Evening — where your ideas move from "brain to build" faster than you can hit Ctrl+S. Even…
🔥6❤3
🚀 GDG Monthly Meetup #2601 - Google DeepMind We are kicking off the new year with a special guest from Google DeepMind! Join us as Thorsten Schaeff takes us under the hood of Google’s latest AI stack. ✨ Gemini 3: The next evolution is here. 🍌 Nano Banana Pro: Deep dive into the capabilities (Yes, it's real!). 🛠️ Google Antigravity: Build faster, ship smarter. Event Details: 📅 Friday, January 16, 2026 🕗 6:30 PM - 9…
⚡7🔥1
Showing the 12 most recent of 20 posts we hold for @GoogleDevSpaceSG. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“Google Developer Space Singapore” (@GoogleDevSpaceSG), 4,917 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/GoogleDevSpaceSG.
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.