Canberra Crescent Residences

Where the stacks are. Each stack’s outline is traced from the developer’s site plan and fitted to the land parcel on the map. Expect positions within a few metres and bearings within a few degrees. Unit types come from the colour the site plan gives each stack and add up to the published unit mix, and the map uses those same colours; 32 of the 32 stacks are also named on the developer’s floor plans, and all of those match.

Facing. The facing is the side the living room and balcony are on, read from the developer’s floor plan for each of the 32 stacks. End and corner homes also have bedroom windows on a second side, which the tool does not model.

What it looks onto. The pools, lawns, courts and pavilions are read off the developer’s site plan and placed on the map with the same fit as the stacks, so they are right to within a few metres. A stack “looks onto” a pool when at least a quarter of 17 sight lines across its window (40° either side of the facing) reach the water before another tower of the project. It “faces out of the estate” when the site boundary is within 50 m straight ahead. Facility names and positions are the developer’s and can change before completion.

Heights. Towers use the developer’s storey counts at an assumed 3.3 m per storey. Buildings standing around the estate use the height in the Singapore Land Authority’s 3D model, read off OneMap 3D on 2 October 2026; where one outline covers a tower and its podium, it is cut into its parts. A building not yet in that model (still being built) uses its published storey count at 3.6 m a storey for a condo and 3.0 m for an HDB block, the averages measured for built ones. Every building is modelled as its footprint raised straight up, on level ground: no roofs, balconies, trees or slopes. Not counted: The school plot across Canberra Crescent (URA Master Plan 2025: about 3 hectares zoned Educational Institution (proposed secondary school), nothing built; the developer’s location map marks it "Future Educational Institution"); The housing plot south-west of the site (URA Master Plan 2025: about 2 hectares zoned Residential at plot ratio 2.8, nothing built; no heights published). It is planned, not yet built, and its height is not published, so the stacks that face it are flagged instead.

Sun. The same solar model as the Sun Path & Facing Calculator, checked to within about three minutes, with a building in the way counted as shade. The window is a point at mid-storey height on the middle of the outside wall. Balconies, overhangs and cloud cut real sun further, so read the hours as a ceiling.

Sun across the year and coolest stacks. The year grid tests the window every half hour on the 15th of each month. Coolest stacks ranks by the average of those twelve days in hours of direct sun after 2pm, least first, at the middle storey of each stack with shade from other buildings taken off; the hours for the whole day sit beside it. For a home at the end of its block the afternoon figure also counts the sun on its end wall.

Floor plans. The developer’s own pages, unaltered, matched to each stack by the layout code on the developer’s schematic diagram. A stack the plan lists as a mirror unit is the plan flipped. Floor plans: Kheng Leong and Low Keng Huat, Canberra Crescent Residences e-brochure. Developer's plans, approximate and subject to change.

Prices. Prices are the developer’s price list, as at 15 Oct 2026: its asking price for each home by unit number, with sold homes marked and “price on application” where the list gives none, read once a day. Anything the developer has not published is not shown. The “Prices + budget” button paints every unsold home by that asking price and greys the sold ones and any the list shows without a price; nothing is estimated. Prices and what is left change, so ask for the latest before you decide. Details are as at 2026-10-02 and can change. Sources: Developer’s e-brochure; Developers’ corporate sites; URA developer sales and caveats; URA land lot map and Master Plan 2025; HDB Property Information; OpenStreetMap; OneMap.