What Sales Records Can Show
NSW property sales records may include a property identifier, locality, contract date, settlement date, sale price, land area, zoning, and property type. The available fields vary between records and source releases.
The most useful part of a sales record is that it records a completed transaction. It can help answer simple questions such as what sold in an area, when it settled, what price was recorded, and whether the property was broadly similar to another property being checked. When several relevant records are considered together, they can provide useful background for understanding local market activity.
Sales data is not the same as an appraisal, valuation, or market forecast. The recorded price may reflect a particular property condition, contract terms, development potential, relationship between parties, partial interest, multi-lot arrangement, or timing factor that is not obvious from the core data fields. Treat the record as evidence to investigate, not as a final conclusion.
How To Use The Sales Page
Start with the place you care about, then narrow the list by date, price, property type, land size, or other available filters. A small set of comparable records is usually more useful than a broad suburb-wide list.
A practical workflow is to begin with a suburb or LGA and a realistic date range. Then remove records that are clearly not comparable because of land size, property type, zoning, or price range. If the list is still too broad, narrow it further by locality, postcode, nature of property, or land area. The goal is not to find the largest possible list; it is to find records that are similar enough to deserve closer checking.
The map view can help when location matters. A sale on the edge of a suburb, near a major road, close to infrastructure, or in a different zoning context may not be comparable to a sale that looks similar in a table. Use the map to understand where records sit, then return to the table fields to check the details.
What To Check Carefully
Sale records can be delayed, amended, duplicated, or missing useful context. Before relying on a record, check the address, land area, contract date, property type, and any official source material available for that property.
Dates need care. Contract date and settlement date answer different questions. A contract date is closer to the point when the sale agreement was made, while the settlement date is when the transaction completed and was recorded for practical purposes. In a changing market, the difference between those dates can matter.
Land area also needs care. Some records relate to units, strata lots, partial interests, grouped properties, or unusual property components. A price per square metre figure can be misleading if the area field does not represent the same kind of land interest as another record. When a sale appears unusually cheap or expensive, check whether the record type explains the difference before treating it as an outlier.
Duplicate-looking records may also need context. Some source files republish records, and some sales involve multiple lots or components. Komand includes duplicate handling and multi-lot display logic where possible, but users should still read the fields rather than assume every row represents a simple single-property sale.
What The Data Does Not Decide
A recorded sale price does not decide current market value, development potential, lending position, legal status, or planning risk. Those questions need current advice, source documents, and local context.
The data also does not show building condition, contamination, easements, restrictions, leases, negotiated inclusions, settlement adjustments, or the reason a buyer and seller agreed to a price. It may not show whether a property had development approval, whether it was bought for land value, or whether it was part of a broader acquisition strategy.
Use the data to form better questions. For example: which nearby sales look most relevant, which records need to be excluded, whether prices changed across a period, whether larger sites traded differently from smaller sites, and whether planning activity nearby might justify deeper checking. Those questions are useful, but the answers should be checked against source documents and professional judgement.
Combining Sales And Planning Context
Sales records explain past transactions. Planning records can explain part of the forward-looking context around an area. If a suburb has major infrastructure, rezoning discussion, a large State Significant project, or a cluster of development activity, it may be worth reviewing sales and planning records together.
That does not mean every nearby project affects every property. A planning project may be too far away, unrelated to the property type, already completed, refused, modified, or still early in assessment. The useful step is to identify possible context, then decide which records deserve official-source review.
Related Pages
Read more about Komand's data sources and how records are prepared.