Channel
@hdbinsights_bukitpanjang
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003811532854 |
|---|---|
| Type | Channel |
| Username | @hdbinsights_bukitpanjang |
| Description | Buying or selling in Bukit Panjang? Get local HDB resale insights, price signals and record alerts backed by real data. 📊 Full market view: @hdbinsights |
| Created | Between 1 February 2026 and 17 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hdbinsights_bukitpanjang |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 18:17 | 3 | no change |
| 13 Aug 2026, 03:00 | 3 | first reading |
20 posts held, back to 17 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
🚨 Today's Near Record Analysis · 12 August 2026 🔔 3 Room Flat · High Floor 📍 Blk 633A Senja Rd 💲 $549,000 · Previous record $562,888 📉 Short of previous record by $13,888 · 2.5% 📏 67 SQM · 721 SQFT ⏳ More than 86 years lease remaining For 3 Room Flat owners in Bukit Panjang, this result is worth watching because it shows the market is still active near record territory. 🟡 This sale came close enough to deserve att…
📊 Bukit Panjang Daily Sale Update · 12 August 2026 One home in Bukit Panjang sold just below the current town high. 1️⃣ High Floor 3-Room Flat at Blk 633A Senja Rd 💲 $549,000 · $761 PSF 📏 67 SQM · 721 SQFT 📈 Close to the 3-Room Flat town record 📩 The next record in Bukit Panjang may be closer than it looks. If you have been wondering about your flat’s value, now is a good time to check. Message us to check how mu…
📊 Bukit Panjang Weekly PSF Watch · Week 32 Based on transactions between 3 August and 9 August. ────────── 📌 Key Insight Bukit Panjang is showing early signs of premium clustering, with several blocks trading meaningfully above the town median for the same flat type. ────────── 📊 Weekly Median PSF • 5 Room Flat · $524 PSF based on 4 transactions • 4 Room Flat · $491 PSF based on 8 transactions ────────── ⬆️ …
📊 Bukit Panjang Weekly HDB Summary · Week 32 Based on transactions between 3 August and 9 August. ────────── 🔥 Market Activity 14 resale transactions · +40% vs last week ────────── 💰 Million-Dollar Deals • Year To Date: 25 transactions ────────── 🔎 Most Expensive Units Sold This Week 1️⃣ 4 Room Flat at Blk 636B Senja Rd 💲 $685,000 · $692 PSF 2️⃣ 5 Room Flat at Blk 627 Senja Rd 💲 $670,000 · $566 PSF 3️⃣ 5 …
📊 Bukit Panjang Market Update · 7 August 2026 One of the larger and less frequently traded flat types changed hands in Bukit Panjang. 1️⃣ Low Floor Executive Flat at Blk 479 Segar Rd 💲 $638,888 · $475 PSF 📏 125 SQM · 1,345 SQFT 🏠 Rare Executive Flat profile
📊 Bukit Panjang Weekly PSF Watch · Week 31 Based on transactions between 27 July and 2 August. ────────── 📌 Key Insight Bukit Panjang is starting to show selective buyer preference, with 3 blocks trading at least 15% above their flat type town median. ────────── 📊 Weekly Median PSF • Executive Flat · $536 PSF based on 3 transactions • 5 Room Flat · $502 PSF based on 5 transactions ────────── ⬆️ Blocks Showin…
📊 Bukit Panjang HDB Snapshot · July 2026 🟡 Prices were broadly steady, with transaction activity picking up in the latest month. Bukit Panjang's overall median resale price for July 2026 was broadly in line with its recent 3 month baseline. This points to a relatively steady month for resale pricing, with values holding close to the town's recent norm. Transaction activity strengthened from the previous month, addin…
📊 Bukit Panjang Weekly HDB Summary · Week 31 Based on transactions between 27 July and 2 August. ────────── 🔥 Market Activity 10 resale transactions · -66% vs last week ────────── 💰 Million-Dollar Deals • Week 31: 1 transaction • July: 1 transaction • Year To Date: 25 transactions ────────── 🔎 Most Expensive Units Sold This Week 1️⃣ Executive Flat at Blk 180 Lompang Rd 💲 $1,100,000 · $786 PSF 2️⃣ 5 Room Fl…
📊 Bukit Panjang Market Update · 31 July 2026 One of the larger and less frequently traded flat types changed hands in Bukit Panjang. 1️⃣ High Floor Executive Flat at Blk 470 Segar Rd 💲 $750,000 · $536 PSF 📏 130 SQM · 1,399 SQFT 🏠 Rare Executive Flat profile
📊 Bukit Panjang Resale Update · 30 July 2026 Bukit Panjang recorded a million dollar sale. 1️⃣ High Floor Executive Flat at Blk 180 Lompang Rd 💲 $1,100,000 · $786 PSF 📏 130 SQM · 1,399 SQFT 💰 Million-dollar flat
📊 Bukit Panjang Daily Sale Update · 29 July 2026 One sale in Bukit Panjang involved a larger flat type that is not often sold. 1️⃣ High Floor Executive Flat at Blk 467 Segar Rd 💲 $710,000 · $507 PSF 📏 130 SQM · 1,399 SQFT 🏠 Rare Executive Flat profile
📊 Bukit Panjang Weekly PSF Watch · Week 30 Based on transactions between 20 July and 26 July. ────────── 📊 Weekly Median PSF • 3 Room Flat · $682 PSF based on 6 transactions • Executive Flat · $556 PSF based on 3 transactions • 4 Room Flat · $552 PSF based on 10 transactions • 5 Room Flat · $524 PSF based on 9 transactions ────────── ⬆️ Blocks Showing Consistent Price Premium These blocks have consistently tra…
Showing the 12 most recent of 20 posts we hold for @hdbinsights_bukitpanjang. 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“HDB Insights Bukit Panjang” (@hdbinsights_bukitpanjang), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hdbinsights_bukitpanjang.
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.