Rental bond data: why it beats listing prices

What a bond lodgement actually is

Every time a new residential tenancy starts in Australia, the tenant's bond, typically four weeks' rent, gets lodged with a state authority as security for the landlord. That lodgement is a government record: a timestamped, dollar-denominated fact about a real lease that just started, filed separately from anything the property was advertised at. It's the closest thing to ground truth this site has, which is why every rent figure on NestLedger is built from bond data rather than from listing prices scraped off a portal.

Listing prices measure what a landlord is asking. Bond lodgements measure what a tenant actually agreed to pay and then legally registered with a government body. The two numbers can diverge: a listing might sit above the eventual lodged rent after negotiation, or a property might list twice at different prices before it leases. Only the lodgement is a completed transaction. That's the whole case for using this data source over any other: it's not a sample of intentions, it's a record of outcomes.

Who publishes what, and how it differs by state

Five state agencies feed the rent figures on this site, and they don't publish on the same schedule, at the same granularity, or with the same level of detail. That matters more than it sounds: a "current" rent figure in one state can be six months older than a "current" figure in another, purely because of how each agency processes and releases its data.

NSW DCJ and SA CBS report at postcode or suburb level with medians already calculated. QLD RTA reports suburb-level medians directly. Tasmania's Department of Justice is the outlier: it publishes record-level bond lodgements (one row per bond, not pre-aggregated), so NestLedger has to bucket those records into quarterly suburb medians itself, which is also why Tasmanian coverage in this dataset tends to be thinner than the mainland states (see the cheapest suburbs guide for how few Hobart-area suburbs currently clear the sample-size bar). Victoria's roughly six-month lag is the longest of the five, which means a Melbourne figure labelled "current" on this site can be reporting on a quarter that's already half a year old by the time it's published, a gap worth keeping in mind before comparing a VIC figure directly against a NSW one from the same nominal period.

One agency, NSW DCJ, reports by postcode rather than suburb, which means a matching step happens before that data ever reaches a suburb page. NestLedger uses the ABS ASGS postcode-to-suburb concordance to link each postcode's reported median to the individual suburbs sitting inside it, based on geographic centroid matching rather than a state-published lookup table. That's a modelled step, not a directly observed one, and it's the reason a handful of small suburbs sharing one postcode can show up with an identical rent figure on this site: they're all inheriting the same postcode-level median because the source data was never collected at a finer resolution than that.

Lodged vs held: not the same number

Two different metrics show up in this data, and conflating them produces the wrong read on how active a market is. Bonds lodged counts new tenancies registered within a given window: it's a flow, a measure of turnover. Bonds held counts the total stock of active bonds an agency currently has on file for that area, including tenancies that started years ago and simply haven't ended; it's a stock, not a flow.

A suburb can have a large bonds-held figure and almost no recent lodgement activity, which would make it look like an active market when it's actually a low-turnover one with a lot of long-term tenancies. Two real records from the current dataset show the difference:

Punchbowl's 170 lodgements is the figure NestLedger treats as evidence of a real, current rental market. Aarons Pass's 188 held bonds says something about the size of the existing tenant base in that area, but says nothing about whether a new tenant looking today would find an active market or a handful of long-settled leases. This is why the "verified market" filter used throughout this site's guides (the requirement that a suburb clear at least 30 recorded lodgements before its median is treated as reliable) is applied specifically to the lodged figure, not the held one.

Why medians lag listings

A bond-lodgement median reports what tenants who signed leases in a past quarter actually agreed to pay. A listing price reports what's being asked for a property right now, this week. Even in a state with the shortest lag in the table above, that's a three-month gap between "what's on the market today" and "what the government has finished processing and published." In a rising-rent market, the published median will read slightly below where new listings are currently priced; in a falling market, the opposite.

This isn't a flaw specific to this site; it's structural to any dataset built on completed transactions rather than live listings, the same tradeoff a property sales median faces against an asking-price index. The upside is that a bond-lodgement median can't be inflated by unrealistic asking prices that never actually lease, and it can't be distorted by a handful of aspirational listings sitting unsold at the top of a portal search. What it loses in immediacy, it gains in being a number that actually happened.

Small samples and grouped areas

Not every suburb has enough lodgement volume to support a reliable median. A suburb with two or three bonds lodged in a quarter can show a median rent that's really just whatever those two or three specific properties happened to rent for. That's a number that says almost nothing about the broader local market. NestLedger's response is the same 30-lodgement threshold referenced above: below that bar, a suburb's figures are still shown (deleting data isn't the answer), but they aren't treated as a "verified market" in guides that rank or compare suburbs.

There's a second complication layered on top of sample size: several state agencies report bond data at postcode or local-area level, then it gets matched down to individual suburb names. Where multiple small suburbs share a postcode, they can end up showing an identical median rent, and that's not a coincidence, just the coarser boundary the source data was actually collected at. Both of these caveats compound with the biggest gap in current coverage: the bondsLodged field simply isn't populated in the Queensland or Victorian source data this site ingests, so no suburb in Brisbane, Melbourne, or any other QLD or VIC city can currently clear the 30-lodgement filter, regardless of how active its actual market is. Median rents for those cities are still accurate, calculated the same way as anywhere else. It's specifically the lodgement-based "verified market" label that can't be applied there yet.