Enbloc News: Royalville, Asia Garden & Jade Towers

By The Folks @PropTalk - January 10, 2012 2 Comments

Royalville, a residential site located on Bukit Timah Road, is back on the market, with an asking price in the range of $320 million to $370 million.

In the last tender exercise conducted in July last year, the asking price was between $370 million and $400 million.

Assuming a land cost of $320 million, this translates to $1,312psf ppr.

Inclusive of the additional 10% balcony space, this translates to $1,197psf ppr, including an estimated development charge of $1.16 million, says marketing agent Credo Real Estate.

Royalville has a land area of approximately 174,176sqft, with a gross plot ratio of 1.4. It has an allowable building height of up to five storeys.

The tender closes at 2.30pm on Feb 15.

Asia Gardens
Asia Gardens, an 84-unit condominium development located on Everton Road, has an indicative pricing of between $302.6 million and $307.7 million. This translates to about $1,500 to $1,525psf ppr, based on GFA of 201,765sqft.

The plot has a site area of about 72,059sqft and is zoned "residential" with an allowable plot ratio of 2.8 under the 2008 Master Plan.

The tender for Asia Garden will close on Feb 29.

Jade Towers
Jade Towers, which is located along Lew Lian Vale, has an indicative guide price of $108.8 million to $110.8 million, which translates to $826 to $841psf ppr.

There are 72 apartments spread across two 10-storey towers. The site has an area of 92,412sqft with a plot ratio of 1.4 and can be reconfigured to accommodate GFA of 131,702sqft.

"With a near rectangular configuration, the site can be redeveloped into 101 new condominiums averaging 1,200sqft each," said marketing agent Savills Singapore.

The tender for Jade Towers will close at 3pm on Feb 16.

Source: The Business Times/The Straits Times


2 comments to ''Enbloc News: Royalville, Asia Garden & Jade Towers"

  1. Hi,
    The maps for Jade Towers and Asia Garden are mixed up. Its the other way round.

  2. Hi Anonymous (13/2/12, 4:37PM):
    Either nobody noticed the mix-up or nobody is interested in this post! :-)

    Thanks for spotting and informing us of the error. We have since set the maps in their correct places.