Grand Damansara @ Petaling Jaya, Selangor
Skip to content
Register first · every figure carries its register code · malaysiaproperty4u.com
Petaling Jaya, Selangor · licensee GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD. (989980-D) · KPKT 30249-1 · developer code 30249

GRAND DAMANSARA @ Petaling Jaya — registered GRAND DAMANSARA, register code 30249-1, 330 units: 220 Pangsapuri Servis + 110 SOHO, Jadual H on ALL 330 — the SOHO units INCLUDED, vacant possession moved by an APPROVED 12-month extension from 03/08/2026 to 03/08/2027 — licensee GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD., off the Sprint Highway, Daerah Petaling, Selangor

Four facts frame this page, and the first one is a date that has already passed. The KPKT KPKT TEDUH register record, read 15 October 2026, carries pindaanTempohSerahKosong: Ya with tempohTambahanDiluluskan: 12 Bulan — an APPROVED 12-month extension that moved contractual vacant possession from 3 August 2026 to 3 August 2027. The original date is about two and a half months in the past, ccc and vp both read -, and the register nevertheless rates the project Lancar and does not flag it Lewat. The filed advertisement still prints Disember 2026. A buyer’s Schedule H clock is the REVISED register date, not the brochure’s. Second, and it is the best news on the page: the 110 SOHO units are NOT outside the Housing Development Act. One licence, one advertising and sales permit and one pjb record reading Jadual H cover the whole registration.

pindaanTempohSerahKosong: Ya · +12 months · VP 03/08/2026 → 03/08/2027Jadual H on ALL 330 · SOHO INCLUDED330 units · 220 Pangsapuri Servis + 110 SOHOccc: - · vp: - · Lancar · no Lewat flagNO filed built-up schedule · keluasan: 0 on both rowstingkat 40 on both components · register only99-year leasehold · expiry 1 December 2121Licence 30249/10-2027/0248(A) · CURRENTAPDL 30249-1/07-2027/0578(R)-(S) · CURRENT to 27/07/2027Baki 1 unit / Baki 0 unit · effectively sold out

Louis Koh · Director, LK Group Marketing · IQI Realty Sdn Bhd · Registered Estate Agency · replies personally

KPKT 30249-1registered GRAND DAMANSARA — the registered name and the marketing name are the SAME string, character for character
Jadual H on 330 of 330including all 110 SOHO parcels — the converse of the office-suite projects on this site
Two filed statutory bandsRM270,000 – RM915,800 and RM230,000 – RM503,800 — identical on the register at BOTH ends of BOTH components
0 of 330reach the RM2,000,000 Selangor Zone 1 foreign-buyer floor — a flat bar
Developer location graphic at Grand Damansara by Grand Global Heights Development Sdn. Bhd., Damansara, Petaling Jaya, Daerah Petaling, Selangor - illustration only, no distance is read off it
Grand Damansara, Petaling Jaya — the developer’s own location graphic. Illustration only; no distance on this page is read off it.
Executive Suite show unit at Grand Damansara by Grand Global Heights Development Sdn. Bhd., Damansara, Petaling Jaya, Daerah Petaling, Selangor - room not stated by the source
Executive Suite show unit, Grand Damansara. Developer photograph; the source does not state which room.
Answer block — every cell carries the register field or the filed document it came from

Grand Damansara at a glance

Read on 15 October 2026 against the KPKT KPKT TEDUH register record 30249-1, the ONE filed statutory advertisement lodged with Jabatan Perumahan Negara (IKLAN_BROSUR_01; its two sibling files in the same directory were fetched and are genuinely absent, so one document is the whole filed record), the GreenRE registers, the Selangor controlled-price project list, the developer’s own two websites and TWO third-party property portals. Four things frame everything below: an approved 12-month delivery extension whose ORIGINAL date has already passed; Jadual H reaching all 330 units including the 110 SOHO; NO filed built-up schedule of any kind; and a register that says Berfasa while licensing exactly one phase. Where sources disagree, both readings are printed and neither is adjudicated.

Registered scheme name
GRAND DAMANSARAprojek.nama on 30249-1. The registered name and the marketing name are the same string, character for character — no Residensi prefix, no Malay alias, no reversal, no translation. A positive finding worth stating: a client who types Grand Damansara into the public register will find this project. The FILED advertisement itself names nothing — it carries no Nama projek/pemajuan field at all, and the string appears only in the document’s masthead, so the register is the only document that formally carries the name
Licensed developer
GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD. (989980-D)KPKT developer code 30249 · 0 sakit, 0 terbengkalai · no recorded offence flag · jumlahProjek: 1 — a clean record over a sample of ONE licensed project · the company registration number comes from the project microsite footer and one portal, which agree; the filed brochure’s OCR renders it with one spurious trailing character and the register prints no registration number at all · the marketing brand “Grand Global” is the licensee’s own first two words — no JV, no unrelated SPV, no parent-versus-licensee gap, which is unusually clean
Developer licence
30249/10-2027/0248(A) · CURRENT13/10/2022 – 12/10/2027, about twelve months to run at the reading date · the filed advertisement prints the number without the suffix and with garbled spacing; the register prints the (A) suffix · the licence itself has ONE unbroken term — the two expired rows in the register belong to the PERMIT history, not the licence
Advertising & sales permit (APDL)
30249-1/07-2027/0578(R)-(S) · CURRENT28/07/2026 – 27/07/2027, about nine and a half months to run · the FILED advertisement prints BOTH permit fields as XXXXXXXXXXXXX — a placeholder in the number AND in the validity, so both were read off the register instead · permit continuity is CLEAN: the earlier permit expired 27 July 2026 and this one starts 28 July 2026 — no gap · two prior rows read Tamat, one (A) and one (N) on the same serial · the -(S) tail reads STRATA · one portal still publishes the EXPIRED 2026 permit as if it were current, on a panel dated a month after it lapsed
Contract schedule & components
Jadual H · 220 Pangsapuri Servis + 110 SOHOONE pjb object covers the whole registration and it reads Jadual H, with tempohAsal: 36 Bulan · so the 110 SOHO parcels are HDA-protected too: the statutory sale contract, the HDA liquidated-damages formula, the section 7A housing development account, the statutory defect liability period and the Tribunal for Homebuyer Claims reach all 330 · the marketed ground- and first-floor RETAIL podium is in NO register row at all, so nothing here reads across onto it
Units
330The filed advertisement (220 + 110) and the register agree EXACTLY · one portal’s body text says 981 while that same portal’s own KPKT panel says “329 of 330 sold” — it contradicts itself threefold on one page · 330 is used here; 981 is refused · but the question is not closed harder than the evidence allows: maklumatPembangunan reads Berfasa and a second, UNLICENSED scheme is marketed, so a larger unregistered whole is possible
Storeys
40 · REGISTER ONLYtingkat: 40 on BOTH component rows · the filed advertisement’s Bilangan tingkat field is NOT PRINTED · no developer surface states a storey count · and the arithmetic that follows is worth seeing: 330 units over two towers of 40 storeys is about four units per floor, which is implausibly low for 273 ft² studios — independent reason to read 330 as a licensed PHASE rather than the whole built form. That is arithmetic, not evidence
Built-ups
NOT FILED. AT ALL.Luas binaan is NOT PRINTED on the filed advertisement and the register’s keluasan reads 0 on BOTH component rows · so every square-foot figure in circulation — 273 to 936 ft² — is the DEVELOPER’S OWN MARKETING FIGURE, and this page labels it that way every single time · no square-metre figure is published by anybody, so no conversion is offered here
Bedrooms / bathrooms
Per COMPONENT onlyRegister bilik / tandas: Pangsapuri Servis 2, 3 bedrooms / 1, 2 bathrooms · SOHO 1 bedroom / 1 bathroom · NOBODY publishes a room count per TYPE — the developer publishes seven marketed types and not one bedroom, bathroom or car-park figure against any of them · Tempat letak kereta is NOT PRINTED and no source gives a bay count or a per-unit allocation
Filed statutory price bands
Pangsapuri Servis RM270,000 – RM915,800
SOHO RM230,000 – RM503,800Harga jualan unit on the filed advertisement, and the registry band is IDENTICAL at both ends of both components · these are the filed statutory Unit Selling Price bands and nothing else: not a price list, not a quotation, not an offer · no “from” figure appears anywhere on this page — the developer’s own headline is asterisked with “T&C apply”, which makes it conditional on attached terms and therefore unpublishable here even though it is NOT below the filed minimum
Delivery
Contractual VP 03/08/2027 · +12 months, APPROVEDtarikhPjbPertama: 03 Aug 2023 + tempohAsal: 36 Bulan gave serahKosongIkutPjb: 03 Aug 2026 · pindaanTempohSerahKosong: Ya, tempohTambahanDiluluskan: 12 Bulan, tempohPembinaanBaharu: 48 Bulan, serahKosongBaharuIkutPjbPertama: 03 Aug 2027 · ccc: -, vp: -, status.keseluruhan: Lancar, no Lewat flag · the current permit expires 27 July 2027, about seven days BEFORE that contractual date, and no source says whether a further renewal is intended
Take-up
Baki 1 unit / Baki 0 unitThe filed advertisement’s own figures: 1 of 220 Pangsapuri Servis remaining and 0 of 110 SOHO — effectively sold out · one portal dated 28 August 2026 agrees at “329 of 330 sold” · the register’s own peratus reads 90.79 (SOHO) and 91.02 (Pangsapuri Servis), and NOTHING on the record says what peratus measures — there is no peratusSiap and no terjual key. Two government surfaces, two quantities, and one of them is unadjudicable by construction · so this is not a page that sells units; it is a page that explains a building
Tenure
99 Tahun — LEASEHOLD · expiry 1 December 2121Pegangan tanah and Tarikh luput pajakan on the filed advertisement · about 95 years unexpired at the reading date, which most sheets in this series cannot get at all · chargee UOB, named on the filing and corroborated by nobody · Sekatan kepentingan is NOT PRINTED — that is a finding, not a gap: whether State consent is needed to transfer is simply unknown
Approving authority & plan
MAJLIS BANDARAYA PETALING JAYAPlan MBPJ/120100/T/P10/797/2022(7) · MBPJ has jurisdiction only inside Petaling Jaya, so the district is Daerah Petaling, Selangor — Zone 1 for the foreign-buyer threshold · corroborated by the register’s own daerah: “Petaling ” and negeri: Selangor, and by filed coordinates 3.131960, 101.611990 · the /120100/T/P10/ body is the stable MBPJ pattern and this is the sixth project on this site to carry it
Locality
NOT FILEDAlamat tapak is NOT PRINTED; the register has no alamat, no mukim and no poskod for this project; and there is no lot or PT number anywhere · the only site address in circulation is ONE portal’s, in the Kampung Sungai Kayu Ara / Damansara Utama pocket of inner PJ off the Sprint Highway, and its 47400 postcode is ALSO the developer’s own office postcode, so it may be inherited rather than independent · the portal address and the filed coordinate corroborate each other, which is the strongest locational finding available
Green rating
NONE. And this is a REAL negativeNo GRAND DAMANSARA row and no GRAND GLOBAL row in the Platinum, Gold, Silver or Bronze GreenRE registers — and none in the UNTRUNCATED 199-entry certification entry list that sits above them · nobody claims a rating: the project microsite has no awards page, the group About page lists no award, no certification and no green rating · one honest hedge is kept: the plan was approved in 2022 and the first SPA was August 2023, while the Bronze table now starts 4 April 2024 and Silver 26 December 2023, so a pre-2024 provisional rating could not appear in those tier tables — the entry list is what closes most of that gap

Explore related topics

Everything below is either a field on KPKT register record 30249-1, a line on the one filed statutory advertisement, a row in the GreenRE registers, a statement on one of the developer’s own two websites, or a reading from one of two third-party portals — and every one of them is labelled with which.

Why this page reads differently from every brochure on this project

Seven things. Each one is a document this page read and a decision it made in the open, and every one of them is checkable against a code you can type into the public register yourself: 30249-1.

📅

It leads with the extension, because the register does

The headline on this project is a date that has already gone past. tarikhPjbPertama reads 03 Aug 2023 and tempohAsal reads 36 Bulan, which gave a contractual vacant possession date of 3 August 2026. pindaanTempohSerahKosong reads Ya, tempohTambahanDiluluskan reads 12 Bulan and serahKosongBaharuIkutPjbPertama reads 03 Aug 2027. So an approved 12-month extension moved delivery by a year, the ORIGINAL date passed about two and a half months before this reading, ccc and vp both read -, and the register still rates the project Lancar with no Lewat flag. The filed advertisement’s Tarikh dijangka siap still says Disember 2026, which is a stale filed estimate against the register’s own revised date. What a buyer needs to know in one sentence: your Schedule H clock runs to the REVISED date, not to the brochure’s.

✅

It states that the SOHO units ARE protected — as a fact, not a hedge

On project after project on this site a SOHO, suite or office component has turned out to sit OUTSIDE the Housing Development (Control and Licensing) Act 1966, with no statutory contract, no liquidated-damages formula and no Tribunal. Here it is the other way round. The register prints ONE pjb object for the whole of 30249-1 and it reads jenis: Jadual H. Both components sit on ONE developer licence and ONE advertising and sales permit. So the 110 SOHO parcels are sold on the prescribed statutory sale contract, with the HDA liquidated-damages formula, the section 7A housing development account, the statutory defect liability period and access to the Tribunal for Homebuyer Claims. This is the single most useful line available on this project, and it is the converse of the office-suite findings elsewhere on this site. The carve-out that travels with it: the marketed RETAIL podium carries no licence row, no unit count and no filing of any kind, so none of the above may be read across onto a retail lot.

📏

It refuses to present a single square foot as filed

There is NO filed built-up schedule on this project at all. Luas binaan is NOT PRINTED on the filed advertisement, and the register’s keluasan field reads 0 on BOTH component rows — not square metres to convert, a zero. So the standing rule on this site — never take a built-up from a filing’s narrative prose, only from its statutory schedule — resolves here to: there is nothing to take. Every square-foot figure in circulation, from 273 to 936, is the developer’s own marketing figure, and this page says so beside each one, every time it appears. No square-metre figure is published by anybody either, so this page offers no conversion: a metric figure here would be the page’s own arithmetic dressed up as a specification.

🔍

It says the development is PHASED and only one phase is licensed

status.maklumatPembangunan reads Berfasa — phased — and exactly ONE phase is registered: these 330 units. Meanwhile the group’s own current-projects page markets a separate Grand Damansara II in “Damansara, Petaling Jaya”, with its own thumbnail and its own carousel entry. That second scheme has NO KPKT developer licence row, NO advertising and sales permit, NO HIMS filing and NO register entry: the serial walk to 30249-2 returns a client error, the developer-level record prints jumlahProjek: 1, and the Selangor controlled-price project list carries no row for this licensee at all. Said plainly: exactly 330 units are licensed, advertised and HDA-protected. Whatever else is marketed on or beside this site is a NEIGHBOUR, not this product, and nothing crosses from it — not a render, not a built-up, not a facility, not a completion date.

📄

It prints both filed bands and no other price — including the developer’s own

Two filed statutory Unit Selling Price bands exist and both are printed here: Pangsapuri Servis RM270,000 to RM915,800 and SOHO RM230,000 to RM503,800, with the registry band identical at both ends of both components. Each is labelled as the filed statutory band, and each carries the same caveat: not a price list, not a quotation, not an offer. What is NOT here is the developer’s own opening “from” headline. It is asterisked with “T&C apply”, which makes it conditional on terms this page cannot read — so it is barred, even though it is NOT below the filed minimum. That is worth stating precisely, because the usual test on this site is whether a marketing figure sits BELOW the filed floor. Here the test is the asterisk, not the direction. One portal also carries two DIFFERENT “from” figures on one page, its body against its own page description, and a monthly instalment it could not even finish computing. No digits from any of that appear here.

⚠

It publishes no swimming pool, and no distance

Two refusals that a brochure would never make. First: a swimming pool is listed by BOTH third-party portals and by NEITHER of the developer’s own two websites, and no filed document mentions facilities at all. One portal escalates it to a “rooftop infinity pool”, while the developer’s only published level assignment is a Level 7 facilities podium. So this page publishes NO pool — it publishes the disagreement instead. Second: the developer publishes not one distance and not one travel time in TEXT anywhere. Everything positional on its location page sits inside a graphic with no text layer. One portal publishes straight-line metre figures to a handful of places; a second portal names a rail station that nothing corroborates and contradicts the first. And the portal’s own amenity cluster may be measured from the developer’s SALES GALLERY at 10 Boulevard, PJU 6A rather than from the site. So this page carries no distance, no travel time and no “nearest station”. It names the places, and it tells you nobody has measured them.

🔑

It separates what the register knows from what marketing says

Four more disagreements are printed here unresolved rather than tidied away. Completion exists in FOUR versions: the filing’s Disember 2026, the register’s revised 03 Aug 2027, one portal’s “Q2 2027”, and another portal’s Build End: N/A. Build status exists in two: the register’s Lancar with ccc and vp both - against one portal’s “Completed Unit Available”, which is flatly wrong against the register. Units exist in three, all on one portal’s single page. And the developer’s own About page is four years stale on its own arithmetic: it claims 26 years of experience from a 1996 start, while its own footer reads 2026. This page carries “active since 1996”, which is a date you can check, and drops the 26. Three of its superlatives are refused outright for want of any primary support: the “most valuable address” claim, the “new landmark” claim, and “minutes away”.

Project DNA — what is filed, what is marketed, and what is simply absent

Grand Damansara: 330 units on Jadual H, two components, one licensed phase

Two filed components on ONE registration: 220 Pangsapuri Servis and 110 SOHO, both at tingkat 40. The developer markets two towers over a ground- and first-floor retail podium — Tower A as “Lifestyle Suites” and Tower B as “Residences” — and NO source maps Tower A or Tower B onto SOHO or Pangsapuri Servis. The inference is strong: Tower A’s three marketed types run 273 to 471 ft² inside a workspace-and-studio marketing frame, while Tower B’s four run 471 to 936 ft² and the register gives Pangsapuri Servis 2 to 3 bedrooms. It is an inference, it is labelled one, and this page does not state it as fact. What is NOT here, from anybody: a built-up schedule, a land area, a car-park bay count, a facilities text schedule, a site address, a mukim, a lot number, an architect, an engineer and a contractor. The site taxonomy term on this page is condominium and serviced apartment, because 220 of the 330 units are filed Pangsapuri Servis and the developer’s own word is “serviced apartment” — but 110 units are filed SOHO and that is flagged throughout rather than smoothed over.

330units — filing and register agree exactly
220 + 110Pangsapuri Servis + SOHO
40storeys — register only, both rows
0keluasan — NO filed built-up schedule
273–936ft² — DEVELOPER MARKETING figures, not filed
+12months approved — VP 03/08/2026 → 03/08/2027
Lancarccc: - · vp: - · no Lewat
1 / 0Baki unit — effectively sold out
99 yrsleasehold — expiry 1 December 2121
NONEGreenRE — never entered certification

Facilities — three surfaces, three different lists, and one headline absence

The developer publishes its facilities as a GALLERY OF IMAGES with no text list anywhere, and the only level assignment on its entire site is a heading reading “Facilities Podium @ Level 7” sitting above a site-plan image. So exactly one level is published and NOT ONE INDIVIDUAL FACILITY is assigned to a level by any source: a per-level facilities table cannot be built for this project and is not attempted here. Nothing is marked “space only” or shell by anybody either — but with no text schedule on any surface, no fit-out commitment can be established for any facility named below. The filed advertisement has no facilities field at all.

Named by the DEVELOPER

the project microsite · recoverable from image titles only
  • Swing terrace · Hammock · Jacuzzi · Pristine lawn
  • Reading room · Indoor gym · Game room
  • Coworking space — the developer names it and NEITHER portal does
  • An “Overall Facilities” site-plan image under the heading “Facilities Podium @ Level 7”
  • These nine subjects come from the developer’s own image titles and filenames, not from a published list. The home page also prints the group caption “Artist’s Impression”, which establishes that the renders are renders and assigns nothing to anything

Published ONLY by third-party portals

two portals · not the developer, not filed
  • SWIMMING POOL — and one portal escalates it to a “rooftop infinity pool”
  • Basketball · Jogging track · Multi-purpose hall · Barbecue
  • Garden and community garden · Laundry · Playground
  • Adult fitness stations · Yoga deck · Car park
  • Ten of these facilities are portal-only. This page does not present any of them as the developer’s, because the developer does not name them

The pool, in full, because it matters

NOT PUBLISHED by this page
  • The single most-asked facility in Malaysian high-rise is PORTAL-ONLY on this project.
  • Both portals list a swimming pool. NEITHER of the developer’s own two websites names one. No filed document mentions facilities at all
  • One portal calls it a rooftop infinity pool, while the developer’s only published level is a Level 7 podium — so the portal’s own description sits against the developer’s own only level assignment
  • Therefore: this page does not say there is a pool, and it does not say there is none. It says two portals list one and the developer does not, and it refuses to resolve what no document resolves
  • Ask for the strata plan and the facility schedule. That is what settles it

Filed by the statutory advertisement

IKLAN_BROSUR_01 · the only filed document
  • NO facilities field. NO facilities list. NO distances. NO built-up schedule. NO storey count. NO land area. NO car-park figure. NO site address.
  • Both permit fields print as XXXXXXXXXXXXX — a placeholder in the number and in the validity
  • What it DOES carry, and it is more than most: the tenure, the lease expiry date, the chargee, both price bands, both unit counts with their Baki figures, the approving authority in words and the building-plan reference
  • Two sibling files in the same directory were fetched and are genuinely absent, so this one document is the whole filed record

Green rating and awards — a real negative, not a hedge

GreenRE registers · no entry anywhere
  • No GRAND DAMANSARA row and no GRAND GLOBAL row in the Platinum, Gold, Silver or Bronze registers — and none in the UNTRUNCATED 199-entry certification ENTRY list that sits above the tier tables
  • An untruncated entry list with no row for the project and none for the licensee is what turns an inconclusive into a finding: on the reachable evidence this project has never entered GreenRE certification
  • And nobody claims otherwise: the project microsite has no awards page and makes no award claim; the group About page lists no award, no certification and no green rating. There is nothing to borrow and nothing to refuse
  • The hedge that is kept because it is honest: the plan was approved in 2022 and the first SPA was August 2023, while the Bronze table now begins 4 April 2024 and Silver 26 December 2023 — so a PRE-2024 provisional rating could not appear in those tier tables. The entry list closes most of that gap; the tier tables alone would not have
  • No alternative scheme explains the zero either: no BCA Green Mark claim, no LEED claim, no certificate library. The GBI directory would not serve on this read, which is INCONCLUSIVE and never a negative
  • Twenty-two GreenRE rows were examined and refused as decoys on five axes, the densest being a real Damansara serviced-apartment project whose licensee name contains GLOBAL, and two Bronze-rated companies named after Damansara Uptown — the commercial heart of the very locality this project sits in. Different licensees, different schemes, non-residential tools. None of them is this project’s credential

The dates, in order — and the one that governs is the REVISED one

2022Building plan MBPJ/120100/T/P10/797/2022(7) approved by MAJLIS BANDARAYA PETALING JAYA
13 Oct 2022Developer licence 30249/10-2027/0248(A) starts
28 Jul 2023First advertising and sales permit starts — 36 bulan
3 Aug 2023tarikhPjbPertama: the first SPA. The delivery clock starts here, and tempohAsal is 36 Bulan
Oct 2023The developer’s construction-progress page opens its first month tab
Oct 2025The newest progress photographs anywhere — taken 18 October 2025 and uploaded November 2025. No percentage, no work-stage text, nothing since
27 Jul 2026Prior permit 30249-1/07-2026/0866 expires — Tamat
28 Jul 2026Current permit 30249-1/07-2027/0578(R)-(S) starts the very next day — clean continuity, NO gap
3 Aug 2026serahKosongIkutPjb: the ORIGINAL contractual vacant possession date. IT HAS PASSED
Dec 2026The filed Tarikh dijangka siap — Disember 2026, a STALE filed estimate against the register’s own revised date
15 Oct 2026Read today: ccc: -, vp: -, status.keseluruhan: Lancar, no Lewat flag, Baki 1 / Baki 0
27 Jul 2027The CURRENT permit expires — about seven days BEFORE contractual delivery. No source says whether a further renewal is intended
3 Aug 2027serahKosongBaharuIkutPjbPertama: the REVISED contractual vacant possession date, after the approved 12-month extension. THIS is the date a buyer’s Schedule H clock runs to
12 Oct 2027Developer licence expires
1 Dec 2121Lease expiry — about 95 years unexpired at the reading date
Layouts — every figure here is the developer’s marketing figure, because nothing is filed

Seven marketed types, 273 to 936 ft² — and NOT ONE of them is a filed built-up

Read this before any card below. The filed statutory advertisement does not print Luas binaan at all, and the register’s keluasan field reads 0 on BOTH component rows. There is no filed built-up schedule on this project in any form. So the seven sizes below are the DEVELOPER’S OWN MARKETING FIGURES, taken from its own integrated-living page, and every one of them is labelled that way on its own card. No source attaches a bedroom count, a bathroom count or a car-park bay to any single type: the only room data that exists anywhere is the register’s, and the register gives it per COMPONENT — Pangsapuri Servis 2 to 3 bedrooms and 1 to 2 bathrooms, SOHO 1 bedroom and 1 bathroom. No source maps either tower onto either filed component, and no source attaches a price to a size, so this page attaches none. No square-metre figure is published by anybody, so no conversion is offered: it would be this page’s own arithmetic.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Studio Suite — developer figure 273 ft²

Tower A, the developer’s “Lifestyle Suites” · built-up NOT FILED — developer marketing figure · beds, baths and bays NOT PUBLISHED by anybody

273 ft² (developer)NOT a filed built-upLikely the SOHO component

A buyer reading the word “studio” should be told what the filing says: Tower A’s filed component is SOHO, and the register gives that component 1 bedroom and 1 bathroom. The developer’s whole marketing frame around this type is small-office-home-office language — “Curate Your Own Space”, with workspace, workshop or studio, hobby space, investment space, study space, storage space and leisure space named as uses. So this is very probably a studio OFFICE rather than a residential studio. The mitigant is real and it is the best fact on this page: it is still sold on Schedule H, so the statutory protections reach it in full. Which tower holds which filed component is an inference, not a published fact.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Dual Key Suite — developer figure 469 ft²

Tower A · built-up NOT FILED — developer marketing figure · room list NOT PUBLISHED: not a bedroom count, not a bathroom count, not a door count, not an entry count

469 ft² (developer)NOT a filed built-up“Dual key” NOT established

This page does not repeat “dual key” as a fact, and here is exactly why. The developer markets a Dual Key Suite and publishes NO room list for it whatsoever — no bedrooms, no bathrooms, no doors, no entrances. The only room data anywhere is the register’s, and the register gives the SOHO component 1 bedroom and 1 bathroom. A 469 ft² parcel on a one-bedroom, one-bathroom filed component does not support a dual-key description. So the honest statement is: the developer uses the term, the developer publishes no room list, and the register’s counts for that component are one and one. Ask for the drawing with the room list written on it before paying for a second key.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Executive Suite — developer figure 471 ft²

Tower A · built-up NOT FILED — developer marketing figure · the one show-unit photograph on this page is titled to this type

471 ft² (developer)NOT a filed built-upShow unit exists

The show-unit photograph at the top of this page is the developer’s own and its title names this type — and that is as far as the evidence goes. The developer’s source does not state which ROOM the photograph shows, so the caption does not claim one. Note also that Tower A’s Executive Suite at 471 ft² and Tower B’s Type C at 471 ft² carry the SAME marketed built-up across two differently-framed towers, and no source explains the duplication. That is the kind of coincidence a schedule would resolve, and there is no filed schedule to resolve it.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Type C — developer figure 471 ft²

Tower B, the developer’s “Residences” · built-up NOT FILED — developer marketing figure · likely the Pangsapuri Servis component — an INFERENCE

471 ft² (developer)NOT a filed built-upRegister: 2–3 beds per component

The register gives the Pangsapuri Servis component 2 and 3 bedrooms with 1 and 2 bathrooms, for all 220 units together. On a 471 ft² marketed built-up that is worth reading carefully: a two-bedroom layout at that size is possible and common in this market, but NOBODY publishes a room count against this type, so this page does not say how many bedrooms it has. Nor is there any filed figure to check the 471 against: it is the developer’s number, published on the developer’s own page, and the register’s area field is a zero.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Type B — developer figure 686 ft²

Tower B · built-up NOT FILED — developer marketing figure · beds, baths and bays NOT PUBLISHED per type

686 ft² (developer)NOT a filed built-up

The middle of the marketed Tower B range. The filed statutory band for the Pangsapuri Servis component runs RM270,000 to RM915,800 — one band for 220 units, with nothing in any document attaching a part of it to a size. So this page prints the band in the register section and attaches no figure to this card, because any such attachment would be invented. Ask for the price list and the Schedule H floor-area schedule from the sale contract: between them they settle both the size and the price for one specific unit, in writing.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Type A — developer figure 916 ft²

Tower B · built-up NOT FILED — developer marketing figure · second largest marketed type

916 ft² (developer)NOT a filed built-up

916 and 936 ft² sit twenty square feet apart in the developer’s own schedule. Two types that close together are normally distinguished by layout rather than by area — and with no drawing reproduced here and no filed schedule in existence, the distinction cannot be read off anything public. On the filed band, a unit at the top of the Pangsapuri Servis component reaches RM915,800, which is still only about 46% of the RM2,000,000 Selangor Zone 1 foreign-buyer floor — see the register section, where that comparison is done properly.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Type A1 — developer figure 936 ft²

Tower B · built-up NOT FILED — developer marketing figure · the largest figure in circulation on this project

936 ft² (developer)NOT a filed built-upTop of the marketed range

This is the upper end of the 273-to-936 ft² range that every brochure, portal and agent page on this project quotes — and the whole range is the developer’s own, not a filed one. Worth recording because it explains a coincidence elsewhere on this site: an unrelated agent page once carried “40 storeys, 273 to 936 sq ft” under a different project’s name. Those figures are THIS project’s, and they travelled OUT of it. Nothing on that page may be cited for either project.

No layout drawing is published on this page. The developer does publish ten unit-layout and floor-plan drawings, and they are its own drawings — but they are vector files in a format this site’s media pipeline cannot yet accept, so they are not reproduced, not redrawn, not approximated and not substituted. And there is no filed schedule behind them: the built-up on this card is the DEVELOPER’S MARKETING figure, not a filed one.

Types B1 and B2 — NO published built-up at all

Tower B · the existence of these two type codes is evidenced ONLY by the developer’s own drawing FILENAMES · no built-up, no bedroom count, no price

Built-up UNPUBLISHEDFilename-only evidenceDo not expect a schedule

The developer’s own media library carries Tower B drawing files for type codes B1 and B2, while its published schedule covers only A, A1, B and C. So Tower B is laid out with at least six type codes and the developer publishes built-ups for four of them. A FILENAME can be the only evidence that a type code exists — and that is exactly when it must NOT be published as a schedule. So this card records that two further types exist and are undocumented, and invents no size for either. If you are being offered a B1 or a B2, ask for the drawing and the floor-area schedule before anything else.

Four notes that belong under this section rather than inside a card. First, the drawings. Ten unit-layout and floor-plan drawings are published by the developer and all ten are vector files, which this site cannot yet serve — so this section ships with no drawing rather than with a substitute, and the cards will be filled in without anything else on this page changing. Second, the developer’s own drawing titles are CROSSED against its own filenames: on the studio, executive and dual-key pairs, the file whose NAME contains “unit” carries the “floor plan” title and the file whose name does not carries the “unit layout” title. That is a reason to read a drawing rather than trust its label, and it is why none of these cards describes a layout it has not been shown. Third, the RETAIL podium. The developer markets ground- and first-floor retail “suitable for F&B outlets, cafés, drive-through fast food and convenience stores”. It appears in NO register row: no retail unit count, no retail area, no retail licence, no retail permit. It is therefore not a card in this section, and nothing in the statutory protections described on this page may be read across onto a retail lot. Fourth, the decoy that is already on this site. Two draft pages here record an agent page whose meta description read “Grand Damansara” over a completely different project’s content. It is resolved: this project is genuinely 40 storeys with a genuine 273-to-936 ft² marketed range, so the numbers travelled out of here and into somebody else’s template. That page remains unusable for either project.

Location — the district is settled four ways, the locality is NOT FILED, and no distance is published here

Petaling Jaya, Daerah Petaling, Selangor — off the Sprint Highway

The district had to be settled before the foreign-buyer threshold could be looked up, and it settles four independent ways with nothing disagreeing. First, the filed building-plan reference MBPJ/120100/T/P10/797/2022(7), whose MBPJ prefix is a Majlis Bandaraya Petaling Jaya reference and whose /120100/T/P10/ body is the stable MBPJ pattern — the sixth project on this site to carry it. Second, Pihak berkuasa yang meluluskan printed in WORDS on the same filed document as MAJLIS BANDARAYA PETALING JAYA, whose jurisdiction lies only inside Petaling Jaya. Third, the register’s own daerah: “Petaling ” and negeri: Selangor. Fourth, the filed coordinates 3.131960, 101.611990, which are in valid range and sit in inner Petaling Jaya. The LOCALITY is a different matter, and this page says so plainly: it is NOT FILED. Alamat tapak is NOT PRINTED, the register carries no address, no mukim and no postcode for this project, and no lot or PT number exists on any surface read.

Open in Google Maps
Filed coordinates 3.131960, 101.611990 (TEDUH 30249-1, sanity-checked in range)MAJLIS BANDARAYA PETALING JAYA · plan MBPJ/120100/T/P10/797/2022(7)Daerah Petaling, Selangor — register daerah and negeri · Zone 1 for the foreign-buyer thresholdNO site address is filed. Alamat tapak is NOT PRINTED and the register has no address field for the project — the only address ON the filed document is the developer’s own sales showcase at 10 Boulevard, Lebuhraya Sprint, PJU 6A, 47400 Petaling Jaya, which is NOT the siteNO mukim, NO lot or PT number, NO title number is published by any sourceThe postcode is PORTAL-ONLY and may be inherited: one portal publishes a 47400 address in Kampung Sungai Kayu Ara — and 47400 is also the developer’s own office postcode at 10 BoulevardNO distance and NO travel time appears anywhere on this page. See the column on the right for exactly why

Which Damansara this is, and which it is not. “Damansara” spans four local authorities depending on which Damansara is meant, so the exclusion matters as much as the answer. On the filed coordinate and the one portal address that agrees with it, this is the inner-Petaling-Jaya Damansara — the Kampung Sungai Kayu Ara / Damansara Utama pocket, hard by the Sprint Highway. It is NOT Damansara Perdana (also MBPJ, several kilometres north), NOT Kota Damansara, NOT Mutiara Damansara, NOT Damansara Damai, NOT Bandar Sri Damansara (MBPJ but with a Kuala Lumpur postcode — the standing trap), NOT Kwasa Damansara, NOT Damansara Heights (which is Kuala Lumpur under DBKL), NOT Ara Damansara and NOT ParkCity. The exclusion of the two northern Damansaras was done by great-circle arithmetic on two FILED coordinates already on this site, and it is used ONLY to exclude — no distance from it is published here.

Rail — this page names NO station, and that is deliberate

  • The developer publishes an LRT map GRAPHIC with no text layer and names no station anywhere.
  • One portal names an MRT station on the Putrajaya line and gives a straight-line metre figure to it. A SECOND portal names a different station on a different line — corroborated by nothing — and separately repeats the MRT one.
  • So: two portals, two different “nearest” rail answers, a developer graphic with no text, and no filed document that mentions rail at all.
  • This page therefore names no station as the nearest and publishes no metre figure. Naming one would be choosing between two publishers who disagree
  • And there is a measurement problem behind the figure itself: that portal’s amenity distances read like a tight cluster around a single point, and the developer’s office AND its sales gallery are both at 10 Boulevard, PJU 6A — so the cluster may be centred on the SALES GALLERY rather than on the site
  • What closes it: the developer’s own location plan with distances in writing, or the site address as it appears in the sale and purchase agreement

Roads — named by a portal, measured by nobody

  • Sprint Highway — the developer’s own only positional text claim is that the tower is “on the SPRINT Highway”
  • NKVE · LDP — both named by one portal with no distance and no access-point detail
  • No source publishes a distance to any highway entry, and no source publishes a travel time to anywhere. The developer’s location page says only that “an abundance of urban amenities is minutes away” — and NOBODY publishes a measured minute
  • Tempat letak kereta is NOT PRINTED on the filing, no source gives a total bay count and no source maps bays to a type. This page promises no bay

Amenities named with NO distance from ANY source

  • Shopping: 1 Utama · Centrepoint Bandar Utama · The Curve · IKEA and IPC · Atria Shopping Gallery · Glo Damansara
  • Education: The British International School of Kuala Lumpur · First City University College · a national primary school in Bandar Utama
  • Healthcare: KPJ Damansara Specialist Hospital · Columbia Asia · Kelana Jaya Medical Centre · Thomson Medical Centre
  • Recreation: TTDI Park · Bukit Kiara Trail · Tropicana Golf & Country Resort · Bandar Utama Golf Course · The Club Bukit Utama · a badminton centre
  • Every name above comes from one portal’s amenity list, and that portal publishes NO distance for any of them. A handful of other places on that portal carry straight-line metre figures, and this page reproduces none of those figures for the reasons in the rail column
  • The developer’s own location page names not one of these places in text. Everything positional it publishes is inside an image

Land, density and the retail podium

  • Keluasan tanah is NOT PRINTED on the filed advertisement and the register carries no land-area field.
  • The only land figure in existence anywhere is one portal’s 2.76 acres — one publisher, undated and unsourced.
  • So DENSITY cannot be computed from a filed denominator, and this page publishes no units-per-acre figure of any kind. A density computed on a portal’s acreage would be this page’s own arithmetic presented as a specification
  • Nobody calls this project low-density either, so there is nothing to refute — a positive finding, for once
  • The marketed ground- and first-floor retail podium appears in NO register row: no unit count, no area, no licence, no permit. It is not costed, not counted and not protected on anything this page can read

One more thing this page will not do. Adjacency is not a distance, a graphic is not a measurement, and “minutes away” is not a travel time. If no source prints a figure, this page prints no figure — and on this project the developer prints none at all.

The statutory record — the spine of this page, not a footnote

KPKT register and the filed advertisement: GRAND DAMANSARA, register code 30249-1

There is exactly ONE filed document on this project. IKLAN_BROSUR_01 is the filed statutory advertisement particulars; its two sibling files in the same HIMS directory were fetched and are genuinely absent, so the directory discriminates and one document is the whole filed record. It is a better-than-average filing in some fields and a placeholder in others: it prints the tenure, the lease expiry, the chargee, both price bands, both unit counts with their Baki figures, the approving authority in words and the building-plan reference — and it prints BOTH advertising-permit fields as XXXXXXXXXXXXX. Every cell below is a field on 30249-1, a line on that filed document, a row in the GreenRE registers, a statement on one of the developer’s own two websites, or a reading from one of two third-party portals, read on 15 October 2026 and quoted with its own key.

Register codeRegistered scheme nameLicensed developerDeveloper licenceAdvertising permit (APDL)Contract schedule & componentsUnits / storeysBuilt-upsBedrooms / bathrooms / parkingFiled statutory price bandsTenure, restriction & chargeeApproving authority & planDelivery, CCC & VPTake-upGreen ratingLand, charges & retail
30249-1
The ONLY registration on developer licence code 30249. pemaju.jumlahProjek reads 1 and the serial walk closes: 30249-1 hit, 30249-2 client error · and yet status.maklumatPembangunan reads Berfasa — PHASED, with exactly one phase licensed · a separate Grand Damansara II is marketed by the group with NO licence row, NO permit, NO filing and NO register entry, and the Selangor controlled-price project list carries no row for this licensee either · so 330 units are licensed, advertised and HDA-protected, and whatever else is marketed is not
GRAND DAMANSARA
projek.nama on 30249-1, and also projek.nama on the developer-level record · the registered name and the marketing name are the SAME string, character for character — no Residensi prefix, no Malay alias, no reversal, no translation · a client who types the name into the public register will find the project, which is a positive finding worth stating · the FILED advertisement carries no Nama projek/pemajuan field at all — the string appears only in its masthead — so the REGISTER is the only document that formally carries the registered name · and a developer-name search on the string “GRAND DAMANSARA” returns ZERO, because that endpoint matches DEVELOPER names only: the licensee is named for the brand family, not for the project. That zero is not a finding about the project
GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD.
Company registration 989980-D — published by the project microsite footer and by one portal, which agree; the filed brochure’s OCR adds one spurious trailing character; and the REGISTER prints no registration number at all · KPKT developer code 30249 · 0 sakit, 0 terbengkalai, no recorded offence flag · jumlahProjek: 1 — score the licensee and state the sample size: a clean record over ONE licensed project · the group’s 1996-onwards portfolio sits under OTHER companies or outside Malaysia and does NOT corroborate this licensee’s delivery record · a sibling licensee (code 13614) holds a COMPLETED Johor project and shares this licensee’s registered office character for character, its business address, and its e-mail domain — three legs of the same corporate fingerprint, all pointing the same way · that sibling’s credentials, and a Johor project image sitting in this project’s own media library, are NOT this project’s · the register’s lamanWeb reads - with lamanWebUrl: null while TWO live developer websites exist — a null web field is never evidence that no developer site exists · registered office in Jalan Pudu, Kuala Lumpur; business address at 10 Boulevard, Lebuhraya Sprint, PJU 6A, Petaling Jaya
30249/10-2027/0248(A) · CURRENT
13/10/2022 – 12/10/2027, about twelve months to run at the reading date · the filed advertisement prints the serial without its suffix and with garbled spacing; the register prints the (A) · the licence has ONE unbroken term: the two expired rows in the register’s lesen_records array are PERMIT serials, not licence serials, and the field name misleads · do not report them as expired licences
30249-1/07-2027/0578(R)-(S) · CURRENT
28/07/2026 – 27/07/2027, about nine and a half months to run · the FILED advertisement prints the permit NUMBER as XXXXXXXXXXXXX and the permit VALIDITY as XXXXXXXXXXXXXX — a placeholder in both fields, which is why both were read off the register instead · never pass licence validity off as permit validity: they are different instruments with different terms · prior rows 30249-1/07-2026/0866(A)-(S) and ...0866(N)-(S), both 28/07/2023 – 27/07/2026, 36 bulan, both Tamat · an (A) and an (N) on the SAME serial inside one array · CONTINUITY IS CLEAN: the old permit expired 27 July 2026 and the current one starts 28 July 2026. No gap. That is rarer than it should be · the current permit expires about seven days BEFORE the contractual delivery date, and no source addresses whether a further renewal is intended — juxtaposed here, alleged nowhere · one portal still publishes the EXPIRED 2026 permit as current on a panel dated 28 August 2026, a month after it lapsed: it is one generation stale · the -(S) tail reads STRATA
Jadual H · 220 Pangsapuri Servis + 110 SOHO
ONE pjb object covers the whole registration and it reads jenis: Jadual H, with tempohAsal: 36 Bulan · so the 110 SOHO parcels are HDA-protected: statutory sale contract, HDA liquidated damages, the section 7A housing development account, the statutory defect liability period and the Tribunal for Homebuyer Claims reach all 330 units · this is the converse of the office-suite components elsewhere on this site, and it is the single most useful line on this page · the carve-out: the marketed ground- and first-floor RETAIL podium is in NO register row at all, so nothing above may be read across onto a retail lot · no source maps the developer’s Tower A / Tower B onto the filed SOHO / Pangsapuri Servis components — UNADJUDICATED
330 · tingkat 40
Filing (220 + 110) and register agree exactly · tingkat: 40 on BOTH component rows · the filing’s own Bilangan tingkat is NOT PRINTED and no developer surface states a storey count, so 40 is REGISTER-ONLY · one portal’s body text says 981 units while that same portal’s own KPKT panel says “329 of 330 sold” — one publisher, one page, three different figures. 330 governs; 981 is REFUSED · but Berfasa plus an unfiled second scheme leave a larger unregistered whole possible, so the 981 is refused rather than disproved · no block or tower count is filed; the developer markets TWO towers
NOT FILED. AT ALL.
Luas binaan is NOT PRINTED on the filed advertisement, and keluasan reads 0 on BOTH register component rows — not square metres to convert, a zero · so EVERY square-foot figure in circulation is the DEVELOPER’S OWN MARKETING FIGURE: 273, 469, 471, 471, 686, 916 and 936 ft², a range of 273 to 936 · two further Tower B type codes exist on the evidence of the developer’s own drawing filenames alone, with NO published built-up, no bedroom count and no price — recorded, not scheduled · no square-metre figure is published by anybody, so this page offers no conversion · what would close it: the Schedule H floor-area schedule in the sale contract, or the developer’s own unit chart
Per COMPONENT only
Register bilik / tandas: Pangsapuri Servis 2, 3 bedrooms and 1, 2 bathrooms · SOHO 1 bedroom and 1 bathroom · NOBODY publishes a room count per TYPE — the developer publishes seven marketed types and not one bedroom, bathroom or bay figure against any of them · which is why this page does not repeat “dual key” as a fact: the developer publishes no room list for that type, and the register gives its component one bedroom and one bathroom · Tempat letak kereta is NOT PRINTED; no total bay count and no per-unit allocation exists on any surface read
Pangsapuri Servis: RM270,000 – RM915,800
SOHO: RM230,000 – RM503,800
The filed statutory Unit Selling Price bands, exactly as Harga jualan unit prints them — and the public registry band is IDENTICAL at both ends of BOTH components · NOT A PRICE LIST, NOT A QUOTATION, NOT AN OFFER · two components, two bands: they are not interchangeable and this page never merges them · no price per square foot appears here: no per-type price is filed, so any psf figure would be this page’s own arithmetic · and no “from” figure appears here from ANY surface — see the disclosure below for exactly which figures were refused and on what ground
99 Tahun — LEASEHOLD · expiry 1/12/2121
Pegangan tanah and Tarikh luput pajakan, both printed on the filing · about 95 years unexpired at the reading date — and a filed lease EXPIRY DATE is something most filings in this series do not give at all · the remaining term, not the original term, is what a bank and a resale buyer price · Sekatan kepentingan is NOT PRINTED — a finding, not a gap: whether State consent is needed to transfer is unknown, and this page neither asserts nor denies one · Bebanan / gadaian: UOB named as chargee on the filing, and mentioned by NO other surface — uncorroborated rather than contradicted
MAJLIS BANDARAYA PETALING JAYA
Printed in WORDS as Pihak berkuasa yang meluluskan · No. kelulusan pelan bangunan: MBPJ/120100/T/P10/797/2022(7) · prefix and named authority agree, and MBPJ has jurisdiction only inside Petaling Jaya → Daerah Petaling, Selangor → Zone 1 · corroborated by the register’s own daerah and negeri, by filed coordinates 3.131960, 101.611990 in valid range, and by the State list’s own gazetted bandar for Petaling Jaya · there is no unadjudicated district question on this project · the LOCALITY, by contrast, is NOT FILED: no Alamat tapak, no mukim, no poskod, no lot
Contractual VP 03/08/2027 · +12 months, APPROVED
tarikhPjbPertama: 03 Aug 2023 + tempohAsal: 36 Bulan → serahKosongIkutPjb: 03 Aug 2026 · pindaanTempohSerahKosong: Ya · tempohTambahanDiluluskan: 12 Bulan · tempohPembinaanBaharu: 48 Bulan · serahKosongBaharuIkutPjbPertama: 03 Aug 2027 · ccc: - and vp: - on BOTH component rows: NO certificate of completion and compliance, NO vacant possession · status.keseluruhan: Lancar and both komponen rows Lancar, with NO Lewat flag — the register rates it on schedule against the REVISED date · the ORIGINAL date has already passed · FOUR completion dates are in circulation: the filing’s Disember 2026, the register’s 03 Aug 2027, one portal’s “Q2 2027”, and another portal’s Build End: N/A — plus that second portal’s build status of “Completed Unit Available”, which is flatly wrong against ccc: - and vp: - · the only third-party surface that has actually READ the extension is the one that writes “36 months + 12 months” · the developer’s own construction-progress page publishes month tabs from October 2023 to October 2025 and NO percentage, NO work-stage text and no text of any kind — its newest photographs were taken 18 October 2025, so its last published progress is about twelve months stale on a project due in under ten
Baki 1 unit / Baki 0 unit
The filed advertisement’s own figures: Pangsapuri Servis: 220 Unit (Baki 1 unit) and SOHO: 110 Unit (Baki 0 unit) — 1 of 330 unsold, i.e. effectively sold out · one portal, dated 28 August 2026, agrees: “329 of 330 units sold” · the register’s own status.rows.peratus reads 90.79 on the SOHO row and 91.02 on the Pangsapuri Servis row — and the record carries NOTHING that says what peratus measures: there is no peratusSiap key and no terjual key on it · so 90.79 / 91.02 cannot be reported as percent sold OR as percent built. The number is real and its unit is undocumented — two government surfaces, two quantities, unadjudicable BY CONSTRUCTION · the portal’s “329 of 330” is an interpretation of the filing’s Baki figures, not a reading of peratus: the two are not the same quantity and are not reconciled here · the register’s own note says only that component status follows the latest 7(f) report in HIMS · this is therefore not a page that sells units. It is a page that explains a building
NONE — and it is a REAL negative
No GRAND DAMANSARA row and no GRAND GLOBAL row in the GreenRE Platinum, Gold, Silver or Bronze registers, and none in the UNTRUNCATED 199-entry certification ENTRY list above them · on the reachable evidence this project has never ENTERED GreenRE certification · and nobody claims a rating: no awards page on the microsite, no award, certification or green rating on the group About page. Nothing to borrow, nothing to refuse · the honest hedge: the plan was approved in 2022 and the first SPA was August 2023, while the Bronze table now begins 4 April 2024 and Silver 26 December 2023 — a pre-2024 provisional rating could not appear in those tier tables, and it is the ENTRY list that closes most of that gap · no BCA Green Mark claim and no LEED claim exists either, so no alternative scheme explains the zero. The GBI directory would not serve on this read: INCONCLUSIVE, never a negative
Land: NOT FILED · charge: ONE portal only
Keluasan tanah is NOT PRINTED and the register has no land-area field; the only figure in existence is one portal’s 2.76 acres, undated and unsourced · so no density, no units-per-acre and no plot ratio appears on this page · maintenance charge: RM0.44 per square foot, stated by ONE portal as INCLUDING the sinking fund — labelled here as a CHARGE, attributed to one portal, and NOT filed, not in the register and not on either developer surface · get it in writing before relying on it, and ask for the sinking fund as a separate figure, which nobody publishes · the Akaun HDA section 7A account number is NOT PRINTED — the account must exist under Jadual H, but its number is not published · architect, engineer, contractor and quantity surveyor: ALL NOT PRINTED, and no contract announcement exists because the licensee is private and no named contractor is listed — the one route that has rescued storey counts and contract sums on other projects is closed here

How to check this table yourself in two minutes. Search the public KPKT TEDUH register for the project record 30249-1 or the developer code 30249 — and on this project, unusually, searching the NAME works too, because the registered name and the marketing name are the same string. What will NOT work is a DEVELOPER-name search on “Grand Damansara”: that endpoint matches developer names only, and it returns zero because no licensee in Malaysia is called that. The zero is about the endpoint, not about the project. The filed advertisement itself sits in the HIMS file store under the developer code, and it is the document that carries the price bands, the tenure, the lease expiry, the chargee and the Baki figures quoted above.

Statutory particulars read 15 October 2026 from KPKT register record 30249-1 and the filed statutory advertisement particulars IKLAN_BROSUR_01. The two filed statutory Unit Selling Price bands above are the filed statutory bands and nothing else: not a price list, not a quotation, not an offer. Figures attributed to a portal are that portal’s, not the developer’s and not filed. Marketing information only — the price list and the sale and purchase agreement at the sales gallery are the only documents that bind.

What Jadual H gives all 330 units — the 110 SOHO parcels included

All 330 units at Grand Damansara are sold on Jadual H, and this page states that flatly rather than hedging it. The register prints ONE pjb object for the whole of 30249-1 and it reads jenis: Jadual H with tempohAsal: 36 Bulan; both filed components sit on ONE developer licence, 30249, and under ONE advertising and sales permit, 30249-1/07-2027/0578(R)-(S). So for every one of the 330, SOHO parcels included: the prescribed statutory Schedule H sale contract rather than a freely negotiated one; the statutory delivery period, here extended to 48 months by an approved amendment; the Schedule H liquidated-damages formula if that period is missed; the section 7A housing development account, into which a purchaser’s money must be paid; the statutory defect liability period running from vacant possession; and access to the Tribunal for Homebuyer Claims. Why this paragraph comes first, and why it is the best news on the page. Project after project on this site has had to be re-framed because a SOHO, suite or office component turned out to sit OUTSIDE the Housing Development (Control and Licensing) Act 1966 — no statutory contract, no liquidated-damages formula, no housing development account, no Tribunal. Here it is the other way round: the 110 units the developer markets with workspace-and-studio language are filed SOHO and they are HDA-protected anyway. A buyer of a 273 ft² “Studio Suite” on this project gets the same statutory contract as a buyer of a 936 ft² Tower B unit. THE ONE CARVE-OUT, and it is a real one. The ground- and first-floor RETAIL podium the developer markets appears in NO register row: no retail unit count, no retail area, no retail licence, no retail permit. Nothing above may be read across onto a retail lot, and this page makes no statement about what contract form a retail lot would be sold on, because no document says. Check all of this with the CODE rather than the name: 30249-1, licence 30249/10-2027/0248(A).

The approved 12-month extension — and why the brochure’s date is the wrong one to plan around

This is the most important paragraph on the page for anyone buying here, so it is written out in full. The register’s delivery block reads: tarikhPjbPertama: 03 Aug 2023, tempohAsal: 36 Bulan, serahKosongIkutPjb: 03 Aug 2026 — and then pindaanTempohSerahKosong: Ya, tempohTambahanDiluluskan: 12 Bulan, tempohPembinaanBaharu: 48 Bulan, serahKosongBaharuIkutPjbPertama: 03 Aug 2027. In plain words: the first sale and purchase agreement was signed on 3 August 2023, the original contractual vacant possession date was 3 August 2026, and an APPROVED extension of twelve months moved it to 3 August 2027. Three things follow, and all three are uncomfortable to print. First, the original date has ALREADY PASSED — about two and a half months before this reading. Second, there is no CCC and no vacant possession on the record: ccc and vp read - on both component rows. Third, the register nevertheless rates the project Lancar, on schedule, on both components and overall, and does NOT flag it Lewat — because it is measuring against the REVISED date, which is still in the future. And the filed advertisement still prints Tarikh dijangka siap: Disember 2026. That is a stale filed estimate: the register’s own revised contractual date is eight months later. Four surfaces now carry four different completion answers — the filing’s December 2026, the register’s 3 August 2027, one portal’s “Q2 2027”, and a second portal’s Build End: N/A beside a build status of “Completed Unit Available” that is flatly wrong against the register. No document reconciles them and this page does not pretend to. What to do with that as a buyer, stated once and plainly: your Schedule H clock runs from the date of YOUR OWN sale and purchase agreement, and the contractual delivery period on this project is the amended 48 months, not the original 36. The date to plan around is the register’s revised date, not the brochure’s. Then read one more field beside it: the current advertising and sales permit expires 27 July 2027, about SEVEN DAYS before that contractual date. No source says whether a further renewal is intended. This page juxtaposes the two and alleges nothing from the juxtaposition. One corroboration worth giving credit for: of the two third-party portals, exactly one has actually read the extension — it prints a construction period of “36 months + 12 months”. The other has not. And the developer’s own construction-progress page corroborates nothing at all: month tabs from October 2023 to October 2025, no percentage, no work-stage description, no text of any kind, and photographs last taken on 18 October 2025. Its last published progress is about twelve months stale on a project due in under ten months.

Berfasa, one licensed phase, and the sibling with no filing at all

The register says this development is PHASED and licenses exactly one phase. status.maklumatPembangunan reads Berfasa, while pemaju.jumlahProjek reads 1 and the serial walk closes with a client error at 30249-2. At the same time the group’s own current-projects page markets a separate scheme called Grand Damansara II, located as “Damansara, Petaling Jaya”, with its own thumbnail and its own carousel entry beside this one. Grand Damansara II has NO KPKT developer licence row, NO advertising and sales permit, NO HIMS filing and NO register entry. The Selangor State controlled-price project list, version 10 September 2026, carries no row for this licensee at all, and the State quota list carries none either. Said as plainly as it can be said: exactly 330 units on registration 30249-1 are licensed, advertised and HDA-protected. Grand Damansara II is a NEIGHBOUR, not this product, and nothing crosses between them — not a render, not a built-up, not a facility, not a facility level, not a completion date and not a price. It is named here exactly once, as a cross-reference, with that status attached — because a buyer who is shown a plan or a render for “phase two” needs to know that what is being shown is not inside the registration that protects the unit being sold. And one piece of arithmetic that belongs here rather than in a specification table: 330 units over two towers that the register puts at 40 storeys each is about FOUR units per floor, which is implausibly low for a tower marketed with 273 ft² studios. That is independent reason to read 330 as a licensed PHASE rather than as the whole built form — and it is arithmetic, not evidence. It is also why one portal’s 981-unit figure is refused rather than disproved: it may be somebody’s number for a larger unregistered whole.

There is NO filed built-up schedule — so no square foot on this page is presented as filed

This is the biggest single gap on the project and it is worth its own paragraph. Luas binaan is NOT PRINTED on the filed statutory advertisement, and the register’s keluasan field reads 0 on BOTH component rows. On other projects on this site that field has been square metres corroborated to the square foot. Here it is a zero: not a figure in different units, no figure at all. The standing rule on this site is: never take a built-up from a filing’s narrative prose, only from its statutory schedule. On this project that rule resolves to there is nothing to take. So every square-foot figure in circulation — 273, 469, 471, 686, 916 and 936 ft², and the 273-to-936 range that every brochure, portal and agent page quotes — is the DEVELOPER’S OWN MARKETING FIGURE, published on the developer’s own page. Each one is labelled that way on its own card in the layouts section, every time it appears, with no exception. Two consequences. First, no square-metre figure is published by anybody, so this page offers no conversion: a metric figure here would be the page’s own arithmetic dressed as a specification. Second, no price per square foot appears on this page either, for the same reason twice over — no per-type price is filed and no per-type area is filed. What closes it: the Jadual H floor-area schedule inside the sale and purchase agreement for one specific unit, or the developer’s own unit chart in writing. Louis Koh will ask for both.

Foreign buyers — Daerah Petaling is Zone 1, and not one unit reaches the floor

The derivation, in four steps, each of which is checkable. One: the district comes from the filed building-plan reference MBPJ/120100/T/P10/797/2022(7) and from MAJLIS BANDARAYA PETALING JAYA printed in words as the approving authority on the same filed document — MBPJ’s jurisdiction lies only inside Petaling Jaya, i.e. Daerah Petaling. Two: Daerah Petaling sits in Selangor ZONE 1, together with Gombak, Hulu Langat, Sepang and Klang. Three: the Zone 1 minimum purchase price for a foreign buyer is RM2,000,000. Four: the filed statutory MAXIMUM across both components of this project is RM915,800. Therefore, in one sentence: not one of the 330 units in this registration reaches the Selangor Zone 1 foreign-ownership floor at its filed statutory price, so a foreign buyer cannot purchase here at all. The dearest filed unit in the scheme is about 46% of the threshold. This is the simplest answer this question has on any page on this site: the obstacle is the PRICE, and it is not close. It is not a title problem — the product is strata — and it is not a restriction-in-interest problem either, because Sekatan kepentingan is NOT PRINTED on the filing, so nothing is known about a consent requirement on the land one way or the other. Two further notes for completeness. The Selangor circular that once created an RM1,500,000 window has EXPIRED and is not current, so it is not applied here. For reference only, and not applicable to this project: the Federal Territory of Kuala Lumpur threshold is RM1,000,000 with Economic Planning Unit consent, and Selangor Zone 3, i.e. Hulu Selangor, is RM1,000,000. Sabak Bernam was not verified for this page and no figure is stated for it. A Malaysian lawyer confirms all of this on the specific parcel; Louis Koh will refer you to one.

Construction progress — and why this page publishes no percentage

Not one construction-progress percentage is published for this project by anybody, and the reason is worth understanding because it looks at first as though two figures exist. The register’s status.rows objects carry jenis, tingkat, bilik, tandas, keluasan, unit, hargaMin, hargaMax, peratus, komponen, ccc and vp — and NOTHING that says what peratus measures. There is no peratusSiap key on this record and no terjual key either. The two values are 90.79 on the SOHO row and 91.02 on the Pangsapuri Servis row. They cannot be reported as percent built, and they cannot be reported as percent sold: the number is real and its unit is undocumented. So this page does not convert them into either claim, and it does not reconcile them against the filing’s Baki 1 / Baki 0, which is a different quantity measured a different way. Two government surfaces, two numbers, one of them unadjudicable by construction — and a register note that says only that component status follows the latest 7(f) report in HIMS. The developer publishes no percentage either: its construction-progress page is month tabs with no figures and no text, ending at October 2025. What closes it: the developer’s own current 7(f) architect certification, or a site visit. Ask for the first and Louis Koh will arrange the second.

No affordable-housing component, no eligibility test and no transfer moratorium

A clean negative, established from the document rather than assumed. The Selangor housing board’s controlled-price project list, version 10 September 2026, carries NO row for this project and NO row for this licensee: no GRAND row and no GLOBAL HEIGHTS row anywhere in it. Its 126-row State quota list carries none either. Two rows in the same gazetted bandar of Petaling Jaya were examined and refused as decoys — affordable schemes by different licensees — and the nearest miss on the developer axis matches only on the word GLOBAL, in a different bandar. So: no Rumah Selangorku component, no Komersial Mampu Milik component, no household-income eligibility test, and no FIVE-YEAR TRANSFER MORATORIUM reaches any unit in this project. That last point is the one that matters in practice: on a controlled-price unit, a transfer is only permitted five years after the sale and purchase agreement. Nothing like that applies here. Corroborated independently by the filed minimum of RM230,000 against that document’s own controlled-price figures, and by the absence of any affordable-price row on the register. And the methodological caveat that keeps this honest: absence from that list is NOT a negative in general, because the list carries only stock open for application. Here it is being used to exclude an affordable COMPONENT, which is exactly what it can do.

What nobody publishes about this project — and the document that would close each one

Seventeen things a buyer would reasonably ask and no source answers. Each is followed by what would actually close it. One, the site address. → the property description in the filed Jadual H sale contract, or the MBPJ development-order file for plan MBPJ/120100/T/P10/797/2022(7). Two, the lot or PT number, and three, the mukim. → an official land search on the parcel. Four, an official postcode. → the same two documents; the only postcode in circulation is a portal’s and may be inherited from the developer’s own office. Five, the ENTIRE built-up schedule. → the Schedule H floor-area schedule, or the developer’s own unit chart. Six, the land area — and therefore density. → the land search, or the development order. Seven, car parking: no total bay count and no per-unit allocation from ANY source. → the strata plan and the developer’s written allocation. Eight, which tower is the SOHO and which the Pangsapuri Servis. → the developer in writing, or the sale contract’s own description of the parcel. Nine, built-ups, bedrooms and bathrooms for Tower B types B1 and B2, whose existence is evidenced only by drawing filenames. → the developer’s unit chart. Ten, bedroom and bathroom counts per TYPE: the register gives them per component and nobody gives them per type. → the layout drawings with the room list on them. Eleven, whether the “Dual Key Suite” is actually dual-key — no room list, no door count, no entry count. → the drawing, and the sale contract’s floor plan. Twelve, the storey count on a FILED document: the 40 comes from the register alone. → the approved building plan. Thirteen, the retail podium: unit count, areas, and whether any lot is for sale rather than for lease. → the developer in writing; nothing about it is on the register at all. Fourteen, the section 7A housing development account number. → the sale contract itself. Fifteen, Sekatan kepentingan — NOT PRINTED, so whether State consent is needed to transfer is unknown. → the land search or the issue document of title. Sixteen, whether the advertising and sales permit will be renewed past 27 July 2027, about a week before contractual delivery. → the developer in writing. Seventeen, the architect, the civil and structural engineer, the main contractor, the quantity surveyor, any construction-progress percentage, the GDV, and a facilities-by-level schedule — all absent, and with a private licensee and no listed contractor there is no contract announcement to rescue any of them. → the developer in writing. Louis Koh will ask the developer, in writing, for any of the above.

What this page does not publish, and why

Louis Koh’s instruction about his own agency’s project materials is absolute, and this page keeps to it: no price-adjustment figure of any kind appears here — not in English, not in Chinese, not in the page body and not in its structured data. First, the field that had to be handled with care, because the filing itself carries it. The filed statutory advertisement contains a field printed Diskaun Bumiputera, and that field carries a value. The field EXISTS; its value is WITHHELD, and it is recorded nowhere on this page and nowhere in the research behind it. A figure sitting on a public statutory document is exactly the kind that gets copied across in good faith, which is why it is named here and refused here. And the clean negative beside it, stated precisely because the three shapes are easy to confuse: that field is a price concession, it is NOT an ethnic unit quota and it is NOT a lot-title classification. The filing’s ethnic unit-quota field is NOT PRINTED, the register carries no ethnic-quota percentage on this record, and no source anywhere publishes a lot-title classification. So there is no quota figure to withhold — there is no quota row at all. Second, the plain list. No discount, no rebate, no nett price, no promotion, no freebie, no incentive and no commission figure appears anywhere on this page, in either language. Beyond the concession field above, nothing of that kind was found on any surface read — not on the developer’s two websites, not on the filed advertisement, not in the register and not on either portal. Saying which of the two it is — found and suppressed, or genuinely absent — is the difference between a disclosure and a formula. Third, and this project set a new precedent for this site. The developer’s own website carries an opening “from RM___” headline, and it is ASTERISKED with “T&C apply”. It is NOT below the filed statutory minimum — the usual test on this site — and it is still refused, because an asterisked figure is conditional on terms the page cannot read, which makes it an offer figure rather than a price. So the test is the ASTERISK, not the direction. No digits from it appear here. Fourth, one portal publishes TWO DIFFERENT “from” figures on a single page — one in its body and a different one in its own page description. Both are above the filed minimum, and both are withheld on the same asterisk-free but unverifiable ground. The DISAGREEMENT is the finding, and there is no second independent publisher to collapse it against. That same portal also carries a computed monthly instalment with its own loan assumptions, and a “Pros” block containing a literal unfilled placeholder where a monthly figure should be — a number it could not even finish computing. No part of any of that is reproduced here: no instalment, no margin, no tenure, no rate. Fifth, returns. No yield, no ROI, no rental-return, no gross-return, no leaseback and no guaranteed-rental rate appears on this page — and on this project NOTHING in that family exists on any surface read, so there was nothing to refuse. On a scheme that is effectively sold out, that is worth stating positively. What this page DOES publish on price, and nothing beyond it: the two filed statutory Unit Selling Price bands registered with KPKT and printed on the filed advertisement — RM270,000 to RM915,800 for the 220 Pangsapuri Servis units and RM230,000 to RM503,800 for the 110 SOHO units — always labelled as the filed statutory bands, always as ONE band per component rather than a figure attached to any built-up or any type, and always with the same caveat: this is not a price list, it is not a quotation, and it is not an offer. Those bands are the SPA price ranges, which is the one kind of price figure this site publishes, and the public registry band is identical at both ends of both components. One charge is published, labelled a charge and attributed: a maintenance figure of RM0.44 per square foot which ONE portal states as including the sinking fund, and which neither developer website nor the filing publishes. Get it in writing before relying on it. For the current price list, for the sale and purchase agreement itself, and for anything attaching to one specific unit, speak to Louis Koh and he will get it in writing.

The licensed developer — named from the register, scored on the register’s own sample size

GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD. — developer code 30249

The company that is legally the developer here is GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD., company registration 989980-D, KPKT developer code 30249. And on this project — unusually for this site — the licensee and the marketing brand are not two different things: the brand “Grand Global” is simply the licensee’s own first two words. There is no joint venture, no single-purpose vehicle with an unrelated name, and no parent-versus-licensee gap to warn about. That is worth saying plainly, because on several projects on this site the name on the brochure belongs to a company that holds no licence at all. One small thing to know: there is no company called “Grand Global Sdn Bhd” in the register, so the bare brand is not itself a licensee — and one portal prints the developer as bare “Grand Global”.

Where the registration number comes from, since the register does not give one. 989980-D is published by the project microsite’s own footer and by one portal, which agree character for character. The filed brochure’s machine-read text adds one spurious trailing character to the same string, and TEDUH prints no registration number at all. Two independent surfaces agreeing, against one scanning artefact of the same number, is why this page prints 989980-D.

How to score this licensee honestly: by its register record AND by its sample size. The record is clean — 0 sick projects, 0 abandoned projects, no recorded offence flag, and a licence with one unbroken term. And pemaju.jumlahProjek reads 1: that clean record covers exactly ONE KPKT-licensed project, which is this one. The group’s published history — a portfolio it dates from 1996, including a completed Johor high-rise, a Kuala Lumpur residential project, a Terengganu island resort and an apartment building in Melbourne — sits under OTHER companies or outside Malaysia, and does NOT corroborate this licensee’s delivery record. So the group’s “successful track of records” line is not read here as this licensee’s track record, and a buyer should not read it that way either.

The sibling licensee, and why it is relevant without being transferable. A KPKT developer search on the brand stem returns exactly TWO records: this licensee, and a second company holding a COMPLETED Johor Bahru high-rise under its own licence code. Three legs of the same corporate fingerprint confirm they are the same group: the registered office addresses are identical character for character, the business addresses are the same suite at 10 Boulevard on the Sprint Highway, and the two register e-mail addresses are on one domain. One of those address fields is also internally contradictory in the register — it glues the Petaling Jaya street to a Johor Bahru city and a Selangor state — which is a standing reason never to read a district off a register address field. What does NOT transfer: that sibling’s completion record, its marketing language, and an image of it that sits inside THIS project’s own media library. A different licensee, a different licence, a different state and a different scheme.

The developer’s own words, and the four claims this page refuses to repeat. “Petaling Jaya’s most valuable address” is supported by no price ranking, no transaction data, no index and no third party: it is a bare assertion and it is refused. “A new landmark in Damansara” is refused for the same reason, and with an extra one: no height ranking is published by anybody, and the FILING does not even print a storey count — the 40 comes from the register alone — so no tallest-type arithmetic is possible. “An abundance of urban amenities is minutes away” is refused because nobody, including the developer, publishes a measured minute. And the About page’s “with 26 years of experience” is four years stale on its own arithmetic: 1996 plus 26 is 2022, while the same site’s footer reads 2026. So this page carries “active in property development since 1996” — a date, which is checkable — and drops the 26. What the developer does publish usefully: that Tower A is “Lifestyle Suites” and Tower B is “Residences”, that the facilities podium is at Level 7, that the renders are an “Artist’s Impression”, and that the retail is intended for food and beverage outlets, cafés, drive-through fast food and convenience stores.

Imagery: what is on this page, and the refusals behind it. Only TWO images on this page come from the developer, and both are the developer’s own: a location graphic and one show-unit photograph whose title names the Executive Suite type. The location graphic is a LOCATOR and nothing else — no distance anywhere on this page is read off it, because it carries no text layer at all. The show-unit photograph is captioned as a show unit and nothing more: the developer’s own source does not state which room it shows, and a caption cannot be transferred between files, so none is invented. Three refusals, and the third is the sharpest thing found on this developer’s surfaces. First, the developer’s own media library contains licensed stock photography — one file whose CMS title IS a stock-agency caption string, truncated mid-word, and another named after an image-library contributor. Both are large and clean technically, and both are refused on PROVENANCE: a stock armchair is not a Grand Damansara interior. Second, images of other projects, including the group’s Johor tower and an apartment building in Melbourne, sit in the same library and are refused for the obvious reason. Third — and this is why a caption is never moved between files on this site — the developer’s own page prints a photographer credit for ONE stock image beneath the OTHER one. The attribution has already been crossed upstream, by the developer, on its own website. Anyone who trusted that caption would publish a stock photograph as a Grand Damansara interior and credit it to the wrong agency.

And two register fields that are worth reading as evidence rather than as metadata. The register’s lamanWeb field reads - with lamanWebUrl: null, while TWO live developer websites exist and both carry this project — so a null web field in this register is never evidence that no developer site exists. That is the fourth time this has been recorded on this site. The lesen_records array, whose name says licences, holds PERMIT serials: two expired permit rows, one with an (A) suffix and one with an (N) on the same number. The licence itself never lapsed, and reporting those two rows as expired licences would be simply wrong.

Licensee particulars read 15 October 2026 from the KPKT KPKT TEDUH register developer record for code 30249 and project record 30249-1, the filed statutory advertisement, the developer’s own two websites, the GreenRE registers, the Selangor State housing lists and two third-party property portals. Nothing on this page is an offer, a quotation or a price list.

Questions a buyer actually asks — answered from the register, or answered “nobody publishes it”

Grand Damansara: the questions, and the honest answers

When will Grand Damansara actually be handed over?
The contractual date is 3 August 2027, and that is the revised one. The KPKT register records tarikhPjbPertama: 03 Aug 2023 with tempohAsal: 36 Bulan, which gave an original contractual vacant possession date of 3 August 2026 — and then pindaanTempohSerahKosong: Ya, tempohTambahanDiluluskan: 12 Bulan, tempohPembinaanBaharu: 48 Bulan and serahKosongBaharuIkutPjbPertama: 03 Aug 2027. So an approved 12-month extension moved delivery by a year. The original date has already passed, there is no CCC and no vacant possession on the record, and the register still rates the project Lancar with no Lewat flag — because it is measuring against the revised date. Four surfaces give four different completion answers:
SurfaceCompletionStatus
Filed statutory advertisementDisember 2026Stale filed estimate
KPKT register, revised contractual VP03 Aug 2027The date that governs a buyer’s contract
One portal“Q2 2027”Its own text also reads the extension correctly as 36 + 12 months
A second portalBuild End: N/AAnd it states “Completed Unit Available”, which is flatly wrong against ccc: - and vp: -
Your own clock runs from the date of YOUR sale and purchase agreement, over the amended 48-month period. Plan around the register’s revised date, not the brochure’s December 2026. One more field beside it: the current advertising and sales permit expires 27 July 2027, about a week before the contractual date, and no source says whether a further renewal is intended.
Are the 110 SOHO units protected under the Housing Development Act, or are they outside it?
They are INSIDE it, and this is the best fact on the project. The register prints one pjb object for the whole of 30249-1 and it reads jenis: Jadual H. Both filed components — 220 Pangsapuri Servis and 110 SOHO — sit on ONE developer licence and ONE advertising and sales permit. So all 330 units get the prescribed statutory Schedule H sale contract, the Housing Development Act liquidated-damages formula, the section 7A housing development account, the statutory defect liability period from vacant possession, and access to the Tribunal for Homebuyer Claims. That is the opposite of several office-suite and serviced-suite components documented elsewhere on this site, where none of those protections reached the parcel being sold. The carve-out: the marketed ground- and first-floor retail podium appears in NO register row at all, so nothing in this answer may be read across onto a retail lot.
How big are the units?
Nobody has filed an answer, and that is the honest reply. Luas binaan is NOT PRINTED on the filed statutory advertisement, and the register’s keluasan field reads 0 on both component rows — a zero, not a figure in other units. So every square-foot figure in circulation is the DEVELOPER’S OWN MARKETING FIGURE: 273, 469, 471 and 471, 686, 916 and 936 ft², a marketed range of 273 to 936. This page prints those figures because the developer publishes them, and labels every one of them as the developer’s rather than as filed, every time. Two further type codes exist in Tower B on the evidence of the developer’s own drawing filenames alone, with no published built-up at all. No square-metre figure is published by anybody, so this page offers no conversion. What settles it for one specific unit is the Jadual H floor-area schedule inside the sale and purchase agreement.
How many units are there — 330 or 981?
330, and the two government surfaces agree exactly. The filed advertisement gives Pangsapuri Servis: 220 Unit and SOHO: 110 Unit, and the register’s two component rows give 220 and 110. One portal’s body text says 981 units — while that same portal’s own KPKT panel on the same page says “329 of 330 sold”. One publisher, one page, three different figures; its own panel agrees with the register against its own prose. So 330 governs and 981 is refused. But the question is not closed harder than the evidence allows: the register’s own maklumatPembangunan reads Berfasa, i.e. phased, and a second scheme is marketed with no filing of any kind — so a larger unregistered whole is possible, and 981 may be somebody’s figure for it. Arithmetic worth seeing: 330 units over two 40-storey towers is about four units per floor, which is implausibly low for 273 ft² studios. That is independent reason to read 330 as a licensed PHASE — and it is arithmetic, not evidence.
Is there a swimming pool?
This page does not answer that, and the reason is the answer. Both third-party portals list a swimming pool. NEITHER of the developer’s own two websites names one. No filed document mentions facilities at all. One of those portals goes further and calls it a “rooftop infinity pool”, while the developer’s only published level assignment anywhere on its site is a facilities podium at Level 7. So two publishers assert a pool, the developer does not, and one publisher’s description sits against the developer’s own only level statement. This page prints the disagreement and refuses to resolve what no document resolves. What the developer itself names, and only through its own image titles rather than a published list: a swing terrace, a hammock, a jacuzzi, a pristine lawn, a reading room, an indoor gym, a game room and a coworking space — and that coworking space appears on NEITHER portal. Ten further facilities are portal-only. Nothing is assigned to a level by anybody, so no per-level facilities table can be built for this project. The strata plan and the developer’s own facility schedule settle it; ask for both.
How far is the nearest MRT or LRT station?
This page publishes no distance and names no nearest station, deliberately. The developer publishes not one distance and not one travel time in TEXT anywhere: everything positional on its location page sits inside a graphic with no text layer, and its only positional words are that an abundance of urban amenities is “minutes away”. One portal names an MRT station on the Putrajaya line and gives a straight-line metre figure to it. A second portal names a different station on a different line, corroborated by nothing, and separately repeats the MRT one. So there are two publishers with two different “nearest rail” answers and no filed document that mentions rail at all. Naming one would be choosing between publishers who disagree. There is also a measurement problem behind the figure itself: that portal’s amenity distances read like a tight cluster around one point, and the developer’s office AND its sales gallery are both at 10 Boulevard, PJU 6A — so the cluster may be centred on the SALES GALLERY rather than on the site, whose address is not filed at all. What this page does instead: it names the places that exist nearby according to one portal — shopping centres, schools, hospitals, parks and golf clubs — and tells you that nobody has published a measured distance to any of them. Ask for the developer’s own location plan with distances in writing.
Can a foreign buyer buy a unit here?
No — not at filed prices, and the answer is unusually clean. The district is Daerah Petaling, derived from the filed building-plan reference MBPJ/120100/T/P10/797/2022(7) and from MAJLIS BANDARAYA PETALING JAYA printed in words on the same filed document. Daerah Petaling is Selangor ZONE 1, together with Gombak, Hulu Langat, Sepang and Klang, and the Zone 1 minimum purchase price for a foreign buyer is RM2,000,000. The filed statutory MAXIMUM across both components of this project is RM915,800 — about 46% of that floor. So not one of the 330 units reaches the threshold: 0 of 330. The obstacle is the price and it is not close. It is not a title question — the product is strata — and nothing is known about a restriction in interest either way, because Sekatan kepentingan is NOT PRINTED on the filing. The Selangor circular that once created an RM1,500,000 window has expired and is not applied here. A Malaysian lawyer should confirm this on the specific parcel.
What is the price?
This page publishes two figures and nothing else: the filed statutory Unit Selling Price bands, one per component. Pangsapuri Servis (220 units): RM270,000 to RM915,800. SOHO (110 units): RM230,000 to RM503,800. Both are exactly as Harga jualan unit prints them on the filed statutory advertisement, and the public registry band is identical at both ends of both components. These are the filed statutory bands. They are NOT a price list, NOT a quotation and NOT an offer, and they are not interchangeable between the two components. No “from” figure appears on this page from any surface, including the developer’s own, and no price per square foot appears either — no per-type price and no per-type area is filed, so any psf figure would be this page’s own arithmetic. The register section explains exactly which figures were refused and on what ground. For the current price in writing on one specific unit, ask Louis Koh.
Is it freehold or leasehold, and how many years are left?
Leasehold, and the filing gives the expiry date, which many do not. Pegangan tanah reads 99 Tahun and Tarikh luput pajakan reads 1/12/2121 — about 95 years unexpired at the reading date. The remaining term, not the original 99, is what a bank and a resale buyer price. Bebanan / gadaian names UOB as chargee on the filing, and no other surface mentions a chargee at all — uncorroborated rather than contradicted. Sekatan kepentingan is NOT PRINTED, which is a finding rather than a gap: whether State consent is needed to transfer this land is simply unknown, and this page neither asserts nor denies one. One portal’s tenure cell reads a bare 2109, which matches nothing filed and is unexplained. It is refused. An official land search settles the lease, the restriction and the express conditions; Louis Koh will order one.
What is “Grand Damansara II”, and is it the same project?
No, and the distinction matters a great deal. The group’s own current-projects page markets a separate scheme called Grand Damansara II in “Damansara, Petaling Jaya”, with its own thumbnail and its own carousel entry. It has NO KPKT developer licence row, NO advertising and sales permit, NO filing in the ministry’s file store and NO register entry: the serial walk to 30249-2 returns a client error, the developer-level record reads jumlahProjek: 1, and the Selangor State project lists carry no row for this licensee at all. Meanwhile the register says this development IS phased — maklumatPembangunan: Berfasa — while licensing exactly one phase. So: exactly 330 units on 30249-1 are licensed, advertised and HDA-protected. Grand Damansara II is a neighbour, not this product, and nothing crosses between them — not a render, not a built-up, not a facility, not a completion date, not a price. If you are shown a plan, a render or a facility for “phase two”, ask which registration it sits on, in writing.
Does Grand Damansara have a green rating?
No, and this is a real negative rather than a hedge. There is no GRAND DAMANSARA row and no GRAND GLOBAL row in the GreenRE Platinum, Gold, Silver or Bronze registers — and none in the untruncated 199-entry certification ENTRY list that sits above the tier tables and that lists projects which have entered certification without yet holding a rating. Nobody claims otherwise either: the project microsite has no awards page and makes no award claim, and the group About page lists no award, no certification and no green rating. There is nothing to borrow and nothing to refuse. The one hedge kept, because it is honest: the building plan was approved in 2022 and the first sale and purchase agreement was August 2023, while the reachable Bronze table now begins 4 April 2024 and Silver 26 December 2023 — so a pre-2024 provisional rating could not have appeared in those tier tables. The entry list is what closes most of that gap. No BCA Green Mark or LEED claim exists on any surface, so no alternative scheme explains the zero. One other Malaysian directory would not serve on this read, which is inconclusive and never a negative.
Is any part of this project affordable housing, with a five-year transfer moratorium?
No. The Selangor housing board’s controlled-price project list, version 10 September 2026, carries no row for this project and no row for this licensee, and the 126-row State quota list carries none either. So there is no Rumah Selangorku component, no Komersial Mampu Milik component, no household-income eligibility test, and no five-year transfer moratorium on any unit here. That last point is the practical one: on a controlled-price unit a transfer is permitted only five years after the sale and purchase agreement, and nothing like that reaches this project. Corroborated by the filed minimum of RM230,000 against that document’s own controlled-price figures, and by the absence of any affordable-price row on the register. Two affordable schemes in the same gazetted bandar of Petaling Jaya were checked and refused as decoys: different licensees, different schemes.
Is the “Dual Key Suite” really a dual-key unit?
Not established, and this page will not repeat it as a fact. The developer markets a Dual Key Suite at a marketed 469 ft² and publishes NO room list for it whatsoever: no bedroom count, no bathroom count, no door count, no entry count. The only room data anywhere is the register’s, and the register gives the SOHO component 1 bedroom and 1 bathroom. A 469 ft² parcel on a one-bedroom, one-bathroom filed component does not support a dual-key description. So the honest statement is: the developer uses the term, publishes no room list, and the register’s counts for that component are one and one. Ask for the drawing with the room list and the door count written on it before paying for a second key — and note that the developer’s own drawing titles are crossed against its own filenames on that very pair of files, which is one more reason to read the drawing rather than its label.
Why are there no floor plans on this page?
Because the developer’s ten drawings are in a file format this site cannot yet serve, and the alternative would have been to substitute something. The developer publishes ten unit-layout and floor-plan drawings as vector files. They are its own drawings and they are the right drawings — and they are not reproduced here, not redrawn, not approximated and not replaced with a lookalike from another project. The layouts section therefore carries the developer’s marketed built-up for each type, an explicit statement that no drawing is published on the page, and nothing invented in the gap. They will be added to the existing cards without anything else on this page changing. Meanwhile, remember what sits behind them: there is no filed built-up schedule at all, so even with the drawings in hand the authoritative area figure for one unit is the floor-area schedule in its own sale and purchase agreement.
Is it a new launch, or can I buy a completed unit?
Neither, strictly — and this page says which and why. The register reads Lancar, under construction, with ccc: - and vp: -: there is no certificate of completion and compliance and no vacant possession, so nothing here is a completed unit, and one portal’s “Completed Unit Available” status is flatly wrong against the register. And it is not usefully a new launch either: the filed advertisement’s own figures read Baki 1 unit on the 220 Pangsapuri Servis and Baki 0 unit on the 110 SOHO — one unit of 330 unsold, i.e. effectively sold out, which one portal dated 28 August 2026 independently reads as 329 of 330 sold. So this page is categorised on built form — condominium and serviced apartment, because 220 of the 330 units are filed Pangsapuri Servis — and it carries no new-launch badge, because a project with one unit left is not a launch whatever its delivery date, and no completed-stock badge either, because there is no CCC. What that means in practice: anything available today is most likely the one remaining unit, a cancelled booking, or a subsale from an existing buyer. Ask, in writing, which it is.
Where exactly is it?
The district is settled. The locality is NOT FILED, and this page says so rather than filling the gap. Settled: Petaling Jaya, Daerah Petaling, Selangor — from the filed plan reference MBPJ/120100/T/P10/797/2022(7), from MAJLIS BANDARAYA PETALING JAYA printed in words on the same document, from the register’s own daerah and negeri, and from filed coordinates 3.131960, 101.611990. NOT filed: Alamat tapak is NOT PRINTED; the register has no address, no mukim and no postcode for this project; there is no lot or PT number anywhere. The only site address in circulation is one portal’s — in the Kampung Sungai Kayu Ara / Damansara Utama pocket of inner Petaling Jaya, off the Sprint Highway, with a 47400 postcode. It agrees with the filed coordinate, which is the strongest locational finding available. But 47400 is ALSO the developer’s own office postcode, so it may be inherited rather than independent. Which Damansara this is NOT, because the name spans four local authorities: not Damansara Perdana, not Kota Damansara, not Mutiara Damansara, not Damansara Damai, not Bandar Sri Damansara, not Kwasa Damansara, not Damansara Heights, not Ara Damansara and not ParkCity. An official land search or the property description in the sale contract is what closes the address question.
Who is the developer, and what is its track record?
The licensee is GRAND GLOBAL HEIGHTS DEVELOPMENT SDN. BHD., company registration 989980-D, KPKT developer code 30249 — and the marketing brand is the licensee’s own first two words, so there is no parent-versus-licensee trap on this project. The register record is clean: 0 sick projects, 0 abandoned projects, no recorded offence flag, and a licence with one unbroken term from 13 October 2022 to 12 October 2027. And the sample size must travel with it: jumlahProjek reads 1. That clean record covers exactly ONE KPKT-licensed project, which is this one. The group’s published portfolio from 1996 onwards — including a completed Johor high-rise, a Kuala Lumpur project, an island resort and an apartment building in Melbourne — sits under OTHER companies or outside Malaysia, and does not corroborate this licensee’s delivery record. A sibling licensee holding the completed Johor tower shares this one’s registered office, business address and e-mail domain, which proves the group link and transfers nothing else. And the group’s own About page is four years stale on its own arithmetic: it claims 26 years from a 1996 start while its footer reads 2026. This page carries the 1996 date and drops the 26.
What does this page refuse to publish, and why?
In summary, and the register section states it in full in its own prose block. No swimming pool, because two portals assert one and the developer does not. No distance and no nearest station, because the developer publishes none and the two portals disagree. No square foot presented as filed, because there is no filed built-up schedule at all. No opening “from” figure from any surface, including the developer’s own, whose headline is asterisked with terms attached. No price per square foot, no monthly instalment, and no figure of the kind Louis Koh’s standing instruction forbids — in either language, in the page body or in its structured data. No density, because the land area is not filed by anybody. No storey count presented as filed, because the filing does not print one. And three superlatives from the developer’s own copy are refused for want of any primary support: the most-valuable-address claim, the new-landmark claim, and “minutes away”. What IS published on price: the two filed statutory Unit Selling Price bands, each labelled as such, neither a price list nor a quotation nor an offer.

Thinking about a unit at Grand Damansara?

Start with the three things this project makes urgent, in this order. First, the handover date that will apply to YOUR sale and purchase agreement — the contractual date on the register is the revised 3 August 2027, not the brochure’s December 2026. Second, the built-up, bedrooms, bathrooms and car-park bays of the specific unit, in writing, because there is no filed built-up schedule on this project at all and no source attaches a room count to any type. Third, what is genuinely available, since the filed advertisement’s own figures say one unit of 330 remains. Then the price in writing, and the maintenance charge in writing. Louis Koh will ask the developer for every one of those.

Louis Koh · Director, LK Group Marketing · IQI Realty Sdn Bhd, Registered Estate Agency. Nothing on this page is an offer, a quotation or a price list. Statutory particulars quoted from KPKT 30249-1 and the filed statutory advertisement, read 15 October 2026. The two filed statutory price bands on this page are the filed bands and nothing else: not a price list, not a quotation, not an offer.

Louis Koh

Director, LK Group Marketing · IQI Realty Sdn Bhd · Registered Estate Agency

More than a decade in Johor Bahru and Kuala Lumpur property, and the reason this page reads the way it does: the statutory record comes first, every hard number carries the register field or the filed document it came from, and where surfaces disagree, both readings are printed and neither is adjudicated. On Grand Damansara that means the approved 12-month extension leads the page rather than hiding in a footnote; the 110 SOHO units are stated to be HDA-protected, because one Jadual H record covers the whole registration; not one square foot is presented as filed, because nothing is; the unlicensed second scheme is named as unlicensed; and the swimming pool, the station distances and the developer’s own asterisked opening figure are all left off the page with the reason given. Ask for any of it and he will get the developer’s answer in writing.

WhatsApp Louis about Grand Damansara

Published 15 October 2026 · last verified 15 October 2026 against KPKT 30249-1, the filed statutory advertisement particulars, the GreenRE registers and certification entry list, the Selangor State controlled-price and quota project lists, the licensed developer’s own two websites and two third-party property portals. Marketing information, not an offer.

Grand Damansara @ Petaling Jaya330 units · 220 Pangsapuri Servis + 110 SOHO · Jadual H on all 330 · contractual VP 03/08/2027 after an approved +12 months
WhatsApp

Ask a specific question

If you would rather not use WhatsApp, use this. I answer them myself. Only your name and one contact method are required.

Email or phone — one is enough

What you send is emailed to me and stored on this site. It goes to no third party, joins no mailing list, and fires no tracking. See the privacy policy.

Developer: Grand Global Group (2 developments on this site)

Where it is: Petaling Jaya (PJ), Selangor

All developers covered

Build progress

The unit mix, the permitted price and how far up it is

None of this table is the developer’s account of itself. It is what the Ministry of Housing and Local Government records from the 7(f) returns: unit type, bedrooms and bathrooms, built-up area, unit count, the price range on the permit, and the certified percentage complete. A brochure price can be revised; the price on the permit was filed. A brochure need not mention progress; the percentage is certified. The status vocabulary is theirs too: Lancar (on schedule), Lewat (behind), Sakit (sick), Terbengkalai (abandoned).

30249-1 · GRAND DAMANSARA

Overall status: Lancar — on schedule

Certified completion by componentSoho – 110 units90.79%Pangsapuri Servis – 220 units91.02%
ComponentBed / bathBuilt-upUnitsPrice on the permitComplete
Soho
40 storeys
Lancar
1 / 1—110RM230,000.00
– RM503,800.00
90.79%
Pangsapuri Servis
40 storeys
Lancar
2, 3 / 1, 2—220RM270,000.00
– RM915,800.00
91.02%

Swipe the table sideways for the rest of the columns.

The filed advertisement · on the ministry’s own server

This is the document the developer had to file, and the housing department had to approve, before it was allowed to advertise at all — served from the ministry’s own host. It normally carries the location plan, the developer licence and building-plan approval references, the expected completion date, the encumbrance position, and the unit count and price floor and ceiling for each type. The brochure a salesperson hands you can be reissued. This one cannot.

Open the filed advertisement (PDF)

Read from teduh.kpkt.gov.my on 2026-10-23, project code 30249-1. Re-read weekly.

What to do with the number. Read it against the delivery date in your own agreement, not against what a salesperson says. A project with a year left on its statutory clock and a third of the building up is telling you something the brochure will not.

How does that compare? Every development on this site, grouped by register status — cancelled, abandoned and behind schedule first.

Where the official drawings are

No floor plan is reproduced on this page — but the drawings are findable

A floor plan is the developer’s copyright. This site does not mirror one and let you assume it is official. What it can do is send you to the drawing itself.

The hardest copy · on the ministry’s server

The advertisement the developer filed and the housing department approved normally carries the location plan and the unit count and price for each type. A salesperson’s brochure can be reissued. This one cannot.

Open the filed advertisement (PDF)

The drawing that binds the developer is the one attached to your own sale and purchase agreement. Anything on any website is a reference copy — check the schedule to your contract before you sign.