The rule behind every "affordable" label on this site
Every affordability verdict on NestLedger, whether comfortable, manageable, stretch, or unaffordable, traces back to one rule: rent shouldn't exceed 30% of gross (pre-tax) income. It isn't a NestLedger invention. It's the threshold used across Australian state housing authorities and Census-based rental-stress reporting, and it's old enough to be treated as the default assumption in most Australian housing-affordability research rather than a live debate. This guide explains exactly how that rule gets applied on this site, walks one suburb through the calculation end to end, and is explicit about what the number leaves out.
The formula itself is fixed: salary needed = (weekly rent × 52) ÷ 0.30. What varies, and what most explanations of the 30% rule skip over, is which weekly rent figure goes into that formula for a given household.
Why household type changes the rent basis
A single renter, a couple, and a family aren't shopping for the same property, so using one rent figure for all three would misstate the calculation for at least two of them. NestLedger's affordability logic resolves this by matching household type to bedroom count: a single-person household uses the suburb's one-bedroom median, a couple uses the two-bedroom median, and a family uses the three-bedroom median. Each household type gets the rent figure that actually corresponds to the size of property it would realistically lease, rather than the all-dwellings median blended across every bedroom count and dwelling type in the suburb.
| Household type | Rent basis used | Why |
|---|---|---|
| Single | 1-bedroom median | Matches a solo renter's realistic lease size |
| Couple | 2-bedroom median | Matches a two-person household's realistic lease size |
| Family | 3-bedroom median | Matches a larger household's realistic lease size |
When a suburb's bond-lodgement data doesn't include a breakdown by bedroom count, which happens in lower-volume areas, the calculation falls back to that suburb's all-dwellings median instead, applied identically across all three household types. That fallback is flagged in the underlying logic as exactly that: a fallback, not a bedroom-matched figure, because a blended median is a less precise input than a true bedroom-specific one.
One suburb, worked through completely
Punchbowl, NSW, in Sydney, is a useful example because it has a full bedroom-type breakdown on record: a $350/week one-bedroom median, a $450/week two-bedroom median, and a $500/week three-bedroom median, backed by 170 recent bond lodgements. Running each household type through the formula:
| Household | Rent basis | Weekly rent | Salary needed (rent × 52 ÷ 0.30) |
|---|---|---|---|
| Single | 1BR median | $350 | $60,667 |
| Couple | 2BR median | $450 | $78,000 |
| Family | 3BR median | $500 | $86,667 |
A single person needs $60,667 a year to clear the 30% line on Punchbowl's one-bedroom median. A family needs $86,667, which is $26,000 more, entirely because the rent basis shifted from a one-bedroom lease to a three-bedroom one, not because of any other adjustment. This is also why comparing a single household's affordability figure against a family household's figure for the same suburb, without accounting for which bedroom basis produced each number, will produce a misleading conclusion: they're answers to two different questions, not two data points on the same scale.
Contrast that with a suburb where the bedroom breakdown isn't available. Aarons Pass, a small Regional NSW locality, has no bedroom-specific rent data on record, only an all-dwellings median of $390/week. There, the fallback applies: single, couple and family households are all assessed against that same $390 figure, producing an identical $67,600 salary requirement for all three. That's not because a family and a single renter in Aarons Pass genuinely need the same income; it's a limitation of the underlying data, not a claim that household size stops mattering there.
The four bands behind every verdict
The 30% line isn't a single pass/fail cutoff on this site; it's the midpoint of a four-band scale that every suburb-and-income combination gets sorted into, from "comfortable" through to "unaffordable":
| Band | Rent share of gross income |
|---|---|
| Comfortable | 25% or less |
| Manageable | Over 25%, up to 30% |
| Stretch | Over 30%, up to 40% |
| Unaffordable | Over 40% |
Take a single renter on the $85,000 reference salary against Punchbowl's $350/week one-bedroom median: $350 × 52 = $18,200 a year in rent, which is 21.4% of $85,000. That lands in the "comfortable" band, with real room below the 30% line, which is a different, more useful statement than simply saying the suburb "passes" the affordability rule. The same household on the $500/week three-bedroom median in the same suburb would be paying $26,000 a year, 30.6% of $85,000, just over the line and into "stretch" territory, despite both figures coming from the same suburb and the same $85,000 income. This banded view is what powers every suburb comparison on this site, not just a single yes/no affordability call.
What the 30% rule ignores
The rule measures one line item, rent, against gross income, and stops there. It doesn't touch groceries, transport, utilities, insurance, or any other recurring cost, and it doesn't distinguish between gross income and what actually lands in a bank account after tax. Two people earning the same salary can clear the 30% rule by an identical margin and still end up in very different financial positions once take-home pay and everyday costs are accounted for.
NestLedger's own default weekly budget assumptions (used for a single-person household across the cost of living calculator) put groceries at $180, transport at $55, utilities at $55, insurance at $45, and other costs at $89 on top of rent. For a single person on Punchbowl's $350/week one-bedroom median, that's another $424 a week beyond rent, which is more than the rent figure itself, before the 30%-rule salary of $60,667 has covered anything except the lease. The 30% rule was never designed to answer "can I afford to live here" in full; it answers the narrower question "is the rent line, on its own, within a standard proportion of income."
It also uses gross income throughout, not take-home pay. Tax, the Medicare levy, and any salary-sacrifice arrangements all reduce what actually reaches a renter's account, and none of that is reflected in the 30%-rule salary figures shown across this site. Two renters clearing the same $490/week ceiling on the same $85,000 gross salary can have meaningfully different weekly take-home pay depending on their individual tax position, because the ceiling doesn't move to account for it.
Where the rule holds up, and where it doesn't
The 30% rule works best as a population-level benchmark: a way to compare affordability across suburbs, cities and time consistently, using a fixed, publicly understood threshold. It works less well as a personal budgeting tool for any individual household, because it can't see anyone's actual debts, dependants, savings goals, or spending habits. A high earner with no debt can rationally spend well above 30% on rent and still be financially comfortable; a low earner with existing debt obligations can be genuinely stretched at well under 30%. NestLedger uses the rule because it's the standard, comparable measure, not because it's a complete description of any one household's situation. For that fuller picture, the cost of living calculator layers a full weekly budget on top of the rent figure, and the rent affordability calculator lets a real income and a specific suburb be tested directly rather than relying on a citywide median.
Where this data comes from
The rent figures used in the worked examples above are from quarterly bond-lodgement data, current as of Q1 2026. The 30% affordability threshold is the standard used across Australian state housing authorities and ABS Census rental-stress reporting, not a NestLedger-defined figure. Full source detail is on the sources page; the complete bedroom-basis and fallback logic referenced in this guide is documented on the methodology page.