Tucson MLS April Closed Transactions Breakdown by Type

Usually we just report the overall averages and numbers of Closed Transactions.   Lately I’ve been doing some breaking down of these numbers into Type of Construction.   I’m going to go back and look at more of these breakdown from previous months this year.   I’ve also started looking for micor trends inside the SFR transactions which are by for the bulk of the closed transactions each month.

Here’s the breakdown by type:

Type
Count
List Price
Sale Price
$SF Sold
% LP to SP
 
SFR
782
$290,365
$277,573
$140
95.5%
TH
101
$213,614
$212,414
$146
94.9%
C
60
$140,826
$133,060
$139
94.4%
MHR
48
$115,706
$111,920
$76
95.5%
MH
9
$80,889
$69,822
$81
86.3%
Total
1000
$264,382
$252,500
95.5%

So you can see the impact on the total numbers residences of different types impact the overall figures.   This is why you should never look at the overall average asking and sales price to determine where the market it at the moment.   It is better to find out what type of construction is involved and narrow your search to that type.

This entry was posted in Tucson Real Estate and tagged , . Bookmark the permalink.

0 Responses to Tucson MLS April Closed Transactions Breakdown by Type

  1. Homes says:

    Not great but good compared to the national average from the last time I checked on the SFRs by about a percent I believe.

    Always nice to know your stats though, that way you can test and track what’s selling well, what offers to accept and where to put you focus.

  2. Homes,

    Considering the mortgage climate of today compared to last year. I think it is great. 1003 closed sales (as of this posting) and we know the buyers are qualified instead of simply being able to fog a spoon.

Leave a Reply

Your email address will not be published. Required fields are marked *

*


− 3 = four

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>