Seaholm Condos

The first condo high-rise announced since 2007 will be downtown Austin’s Seaholm condos.  Officially called the Seaholm Residences, the style of the condos are planned to be “industrial chic” and include the expected bundle of highrise common area amenities, including and exercise and conference rooms, pool, and gym.

280 Units are scheduled for completion in 2015.

Seaholm pricing:

  • Studios begin at $270k
  • 1bds begin at $300k+
  • 2bds begin at $450k+
  • 3bds begin at $1.1mm+
Seaholm condos at 222 West Ave, rendering by STG Design

Seaholm condos at 222 West Ave, rendering by STG Design

We’ve speculated for years about when the next condo high-rise would be announced in downtown.  Seaholm was always a leading contender, in addition to thinking that an apartment building would convert. The latter option not as viable because these days it’s easier to just sell the whole apartment building.

222_west_condos_seaholm_protected_views

Most south and southwest views will be “protected” from future development

The building is oriented lengthwise to the north and south, much like 360 condos. We haven’t seen floor plans, but we expect units with southern facing glass towards the lake to be priced higher, relative to the rest.

***As of 10/29/13 all 280 units have been reserved and buyers are being placed on a wait list.  I’ll be updating downtown buyers as new information is released, contact me here to get updates. 

-Jude

Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>