Median weekly rents by postcode and dwelling type, Queensland
liveThe Median rents by Postcode sheet of the RTA's bond statistics workbook. Each row is one postcode, dwelling type and quarter, with the median weekly rent in dollars paid for new tenancies commencing in that quarter, as recorded from the bonds lodged with the RTA.
Also called: Queensland median rent by postcode, Queensland rental bond data by postcode, RTA median rents postcode, Brisbane rent by postcode.
Part of RTA bond statistics, 2 tables the publisher releases together: Median weekly rents by suburb and dwelling type, Queensland.
- What is in each row?
- The median weekly rent of the new tenancies that began in one Queensland postcode in one quarter for one dwelling type, such as a two bedroom flat or a three bedroom house, as the RTA works it out from the bonds lodged with it. The series runs from the March quarter 2012.
- Why are many medians blank?
- The RTA leaves a cell empty where it gives no median for a postcode, dwelling type and quarter, which is usually because few bonds were lodged. A cell holding an empty string is a null value here, and a cell the workbook leaves wholly empty gives no row.
- How are the dates given?
- As the month that ends the quarter and its year, in two columns, as the RTA's workbook heads them. A row for June 2026 covers tenancies that began from April to June 2026.
Made for agents
Connect your AI agent
Any agent that connects to publicdata.au/mcp can find this dataset, read its 5 fields, count and filter across all 99,470 rows and diff its versions. Every answer names the version and carries RTA's attribution. No key.
Then ask it: What does Median weekly rents by postcode and dwelling type, Queensland hold, and what changed in the newest version?
claude mcp add --transport http publicdata https://publicdata.au/mcpOne command. No key, no account, no sign-up.
Settings, then Connectors, then Add custom connector, and paste https://publicdata.au/mcp.
On the web and in the desktop app.
https://publicdata.au/mcpStreamable HTTP. Cursor, VS Code or any client that connects to a remote MCP server.
Using https://publicdata.au/llms.txt, how many people died on Queensland roads in 2025, by month?For an assistant that reads the web and has no connector.
The dashboard above, live. Click to filter, add panels, share a link or embed a frame.
Query APIFilter and count from a URLaggregate?group=postcode&metric=max.median_weekly_rent&year=eq.2026&dwelling=eq.House%203
Highest quarterly median weekly rent for a three-bedroom house in each postcode in the newest year, in dollars: 1,250 4217, 1,200 4218, 1,175 4221, 1,160 4220.
Download it as Excel, CSV, JSON and 6 more formats
Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version never changes.
In your own tools
Use it in Excel, R, Python and more
Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.
The dated URL in the code never changes. https://publicdata.au/d/qld-median-rents-by-postcode/latest/ redirects to the newest version.
https://publicdata.au/d/qld-median-rents-by-postcode/latest/data.csvIn Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.
https://publicdata.au/d/qld-median-rents-by-postcode/latest/data.csvIn Power BI Desktop choose Get data, then Web, paste this address and choose Anonymous when asked how to sign in. A scheduled refresh reads the same address, so the report follows each new version.
library(publicdataau)
df <- pd_read("qld-median-rents-by-postcode")
pd_attribution(df)install.packages("publicdataau"). pd_read() fetches the version's Parquet file; pd_rows() and pd_aggregate() ask the query API instead, and pd_connect() attaches the DuckDB file.
import publicdata_au as pd_au
df = pd_au.read("qld-median-rents-by-postcode")
df.attrs["publicdata"]["attribution"]pip install "publicdata-au[pandas]". read() fetches the version's Parquet file; rows() and aggregate() ask the query API, and connect() attaches the DuckDB file.
INSTALL httpfs; LOAD httpfs;
ATTACH 'https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/data.duckdb' AS qld_median_rents_by_postcode (READ_ONLY);
SELECT dwelling, count(*) FROM qld_median_rents_by_postcode.records GROUP BY 1 ORDER BY 2 DESC;The DuckDB file attaches read-only over HTTPS and only the blocks a query touches are read. Parquet works the same way: FROM read_parquet(url).
const res = await fetch("https://publicdata.au/api/v1/datasets/qld-median-rents-by-postcode/aggregate?group=postcode&metric=max.median_weekly_rent&year=eq.2026&dwelling=eq.House%203");
const { rows, publicdata } = await res.json();
console.log(rows, publicdata.attribution);The query API answers a page on any site as well as Node, with no key. It returns the rows and the attribution the licence asks for.
What is in it
Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised.
| Field | Type | Publisher's header | Note |
|---|---|---|---|
| postcode | string | (row header 1) | |
| dwelling | string | (row header 2) | |
| quarter_month | string | (column header 1) | The month that ends the quarter, Mar, Jun, Sep or Dec. |
| year | integer | (column header 2) | |
| median_weekly_rent | number | (cell) |
Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is postcode, dwelling, year, quarter_month.
A sample of 10 rows
Rows from the newest year that have a median, with the dwelling types taking turns. A blank cell is shown as null.
| postcode | dwelling | quarter_month | year | median_weekly_rent |
|---|---|---|---|---|
| 4000 | Flat 1 | Mar | 2026 | 619 |
| 4000 | Flat 2 | Mar | 2026 | 835 |
| 4000 | Flat 3 | Mar | 2026 | 1100 |
| 4000 | House 2 | Jun | 2026 | 500 |
| 4000 | House 3 | Mar | 2026 | 850 |
| 4005 | House 4 | Mar | 2026 | 1300 |
| 4006 | Townhouse 3 | Mar | 2026 | 800 |
| 4012 | Townhouse 2 | Mar | 2026 | 650 |
| 4000 | Flat 1 | Jun | 2026 | 600 |
| 4000 | Flat 2 | Jun | 2026 | 850 |
The first row as JSON
As it appears in data.json.
GET https://publicdata.au/d/qld-median-rents-by-postcode/latest/data.json
{
"postcode": "4000",
"dwelling": "Flat 1",
"quarter_month": "Mar",
"year": 2012,
"median_weekly_rent": 430.0
}
Query it without downloading
The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.
How filters work
Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive except with ilike. Prefix not. to negate a filter, as not.eq.value.
| Operator | What it matches |
|---|---|
| eq.value | Equal to the value. |
| neq.value | Not equal to the value. A blank cell does not match. |
| gt.value | Greater than the value. |
| gte.value | Greater than or equal to the value. |
| lt.value | Less than the value. |
| lte.value | Less than or equal to the value. |
| like.*text* | Matches a pattern where * stands for any run of characters. Case-sensitive. |
| ilike.*text* | The same as like, ignoring case. |
| in.(a,b,c) | Equal to any value in the list. A value cannot contain a comma. |
| is.null | Blank in the source, or suppressed by the publisher. |
| Parameter | What it does |
|---|---|
| select | Fields to return, comma-separated. Every field when absent. |
| order | field.asc or field.desc, comma-separated. The publisher's row order when absent. |
| limit | Rows per page, 1 to 10,000. 100 when absent. |
| offset | Rows to skip. The next URL in each answer sets it for you. |
| group | On aggregate, fields to group by, comma-separated. |
| metric | On aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent. |
| format | json, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers. |
Without a version the API answers from the newest loaded version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer that never changes. /api/v1/datasets/<slug>/versions lists the loaded versions. The 1 newest version is loaded; versions lists them.
The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.
https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, or give it to any client that connects to remote MCP servers. Each queryable dataset is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.
Smaller files
The same rows split by a field, one JSON file each. Each file carries the same provenance header.
By dwelling (8 files)
by/dwelling/index.json lists every file with its row count.
What changed
One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal.
- 2026-07-13 99,470 rows5 fieldsxlsx5c3af9c21bb9
versions.json · changes.json · history.tar.zst (90 KB, every version's Parquet and manifest)
Questions
How do I download Median weekly rents by postcode and dwelling type as a CSV file?
Open https://publicdata.au/d/qld-median-rents-by-postcode/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.
Can I open Median weekly rents by postcode and dwelling type in Excel?
Yes. https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/data.xlsx is a workbook with the 99,470 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/data.csv.gz is the CSV at about a tenth of the size.
What years does Median weekly rents by postcode and dwelling type cover?
The current version covers 2012 to 2025. Each release from RTA becomes a new dated version here, and earlier versions stay online.
How often is Median weekly rents by postcode and dwelling type updated?
RTA releases it quarterly. This site checks the portal every week and adds a dated version when the file changes.
Can I use Median weekly rents by postcode and dwelling type commercially?
Yes. CC BY 3.0 AU allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.
Is this the official source for Median weekly rents by postcode and dwelling type?
No. The publisher is Residential Tenancies Authority, and its page is https://www.rta.qld.gov.au/copyright. This site republishes the publisher's file without changing its content. The original sits beside every version as source.xlsx with its SHA-256, so the two can be compared.
How do I get only the rows for one dwelling?
Every version has one JSON file per value of dwelling, 8 files in the current version, listed with row counts at https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/by/dwelling/index.json. For example https://publicdata.au/d/qld-median-rents-by-postcode/v/2026-07-13/by/dwelling/house-3.json holds the 16,240 rows where dwelling is House 3.
What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.xlsx so the change can be checked.
The publisher releases RTA bond statistics as 2 files at once, so all 2 tables here share a version date.