publicdata.au publicdata.au on GitHub

Births, deaths and marriages registered by calendar year, Victoria

live
Publisher Registry of Births, Deaths and Marriages VictoriaUpdated yearlyLicence CC BY 4.0Latest 2026-07-06Rows 48Fields 3

Registered events by calendar year from the Registry of Births, Deaths and Marriages Victoria. Each row is one kind of event, births, marriages or deaths, and one calendar year, with the number the registry registered in that year.

Also called: Victorian births deaths and marriages by year, Births registered in Victoria per year, Deaths registered in Victoria per year.

Part of Births, deaths and marriages registered in Victoria, 4 tables the publisher releases together: Deaths registered per month, Victoria, Marriages registered per month, Victoria, Registrable life events by financial year, Victoria.

Before you use it
What does each row hold?
The number of births, of marriages or of deaths the registry registered in one calendar year. An event is counted in the year the registry registers it, which may differ from the year it happened.
Why does a year's count differ from other published figures?
Counts by registration date can run ahead of or behind counts by the date of the event, for example when registrations are delayed. Other agencies, such as the ABS, may count by the date of the event.
48event years
2010 to 2025years drawn
3fields
9formats
1version
050k100k150k200k2010 Births: 71,6882010 Deaths: 35,7642010 Marriages: 28,5252011 Births: 72,4912011 Deaths: 36,7332011 Marriages: 27,50320112012 Births: 78,7482012 Deaths: 36,2382012 Marriages: 29,9012013 Births: 75,1532013 Deaths: 36,5122013 Marriages: 29,27920132014 Births: 75,3782014 Deaths: 38,9482014 Marriages: 29,7392015 Births: 74,8462015 Deaths: 39,9552015 Marriages: 25,48720152016 Births: 84,4042016 Deaths: 40,0152016 Marriages: 26,2902017 Births: 83,4932017 Deaths: 40,7702017 Marriages: 26,31720172018 Births: 79,7262018 Deaths: 39,6402018 Marriages: 29,9992019 Births: 79,5972019 Deaths: 41,3872019 Marriages: 28,91720192020 Births: 74,6202020 Deaths: 41,1432020 Marriages: 16,6232021 Births: 76,4102021 Deaths: 42,5072021 Marriages: 18,74020212022 Births: 76,1982022 Deaths: 47,9962022 Marriages: 33,2332023 Births: 72,9322023 Deaths: 45,3452023 Marriages: 29,82620232024 Births: 82,3502024 Deaths: 45,9002024 Marriages: 32,0482025 Births: 80,5292025 Deaths: 46,5882025 Marriages: 30,2072025
BirthsDeathsMarriages
Registrations per year by event, 2010 to 2025. The figure is a sum of the events registered column from version 2026-07-06, worked out in the build. Nothing else is added.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 3 fields, count and filter across all 48 rows and diff its versions. Every answer names the version and carries BDM Victoria's attribution. No key.

Then ask it: What does Births, deaths and marriages registered by calendar year, Victoria hold, and what changed in the newest version?

claude mcp add --transport http publicdata https://publicdata.au/mcp

One command. No key, no account, no sign-up.

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 keeps its content.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/vic-registered-events-by-calendar-year/latest/data.xlsx
Download this file

One workbook with a records sheet of 48 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

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/vic-registered-events-by-calendar-year/latest/ redirects to the newest version.

https://publicdata.au/d/vic-registered-events-by-calendar-year/latest/data.csv

In 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.

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.

FieldTypePublisher's headerNote
eventstring(row header 1)Births, Marriages or Deaths.
yearinteger(column header 1)
registrationsinteger(cell)

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is event, year.

A sample of 10 rows

From the latest version, newest first by year registered, then in the publisher's order, with every field. A blank cell is shown as null.

eventyearregistrations
Births202580529
Marriages202530207
Deaths202546588
Births202482350
Marriages202432048
Deaths202445900
Births202372932
Marriages202329826
Deaths202345345
Births202276198
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/vic-registered-events-by-calendar-year/latest/data.json
{
  "event": "Births",
  "year": 2025,
  "registrations": 80529
}

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.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

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 that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess than or equal to the value.
like.*text*Matches a pattern where * stands for any run of characters, ignoring case in the ASCII letters A to Z.
ilike.*text*The same as like. Both ignore case in ASCII letters only, so É and é differ.
in.(a,b,c)Equal to any value in the list. A value cannot contain a comma.
is.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.asc or field.desc, comma-separated. When absent, rows come in the order of the file they are read from. For the newest versions that is the version's own data.parquet, which keeps the publisher's order unless the dataset sorted it. Any other version is read from the Parquet file the answer names in file, and when that file is sorted the answer names its sort in order, which ties follow too.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, 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 version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer from that version alone. Every version with a table can be queried, and /api/v1/datasets/<slug>/versions lists them. A query on a version the database does not hold is read from its Parquet file, and one that would read too much of it is refused with DuckDB SQL that answers it from the file. 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. Its row tools and the query API answer every version through one query path, so a tool's answer and the query URL it cites give the same rows. A query that would read too much of a file is refused with DuckDB SQL that answers it from the file. It also has search and fetch, the two tools ChatGPT's deep research and company knowledge call by name, which run search_datasets and read a dataset's record in the shapes those features expect. 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, connect the publicdata.au plugin in ChatGPT, or give it to any client that connects to remote MCP servers. Each dataset with a table 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.

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.

versions.json · changes.json · history.tar.zst (3.7 KB, every version's Parquet and manifest)

Questions

How do I download Births, deaths and marriages registered by calendar year as a CSV file?

Open https://publicdata.au/d/vic-registered-events-by-calendar-year/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/vic-registered-events-by-calendar-year/v/2026-07-06/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 Births, deaths and marriages registered by calendar year in Excel?

Yes. https://publicdata.au/d/vic-registered-events-by-calendar-year/v/2026-07-06/data.xlsx is a workbook with the 48 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/vic-registered-events-by-calendar-year/v/2026-07-06/data.csv.gz is the CSV at about a tenth of the size.

What years does Births, deaths and marriages registered by calendar year cover?

The current version covers 2010 to 2025. Each release from BDM Victoria becomes a new dated version here, and earlier versions stay online.

How often is Births, deaths and marriages registered by calendar year updated?

BDM Victoria releases it yearly. This site checks the portal every week and adds a dated version when the file changes.

Can I use Births, deaths and marriages registered by calendar year commercially?

Yes. CC BY 4.0 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 Births, deaths and marriages registered by calendar year?

No. The publisher is Registry of Births, Deaths and Marriages Victoria, and its page is https://discover.data.vic.gov.au/dataset/births-deaths-and-marriages-registered-events-by-calendar-year. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. It turned column headers into rows, one row for each value. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.xlsx with its SHA-256, so the two can be compared.

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.

Births, deaths and marriages registered in Victoria is 4 tables here, and each takes its version date from its own file.

Attribution and citation

The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.

Registry of Births, Deaths and Marriages Victoria, Victorian Government, Births, Deaths and Marriages - registered events by calendar year, sourced 3 October 2026, https://discover.data.vic.gov.au/dataset/births-deaths-and-marriages-registered-events-by-calendar-year, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/vic-registered-events-by-calendar-year/v/2026-07-06/

The attribution alone is inside every file. Harvard is the author-date form a report or a brief asks for. Paste the HTML on a web page so the links carry.

Licence record

Registry of Births, Deaths and Marriages Victoria states the licence, CC BY 4.0, on its own page, which was read and recorded here on 1 October 2026.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2026-07-06 read it from discover.data.vic.gov.au on 3 October 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/vic-registered-events-by-calendar-year")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23116261

Each copy carries the same attribution and links back to this page.

For agents and tools

This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.

Source

Registry of Births, Deaths and Marriages Victoria publishes this table on www.bdm.vic.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 3 October 2026. Source SHA-256 91148ea7b16e03e0…

Improve this dataset

This page is built from register/vic-registered-events-by-calendar-year.yaml on GitHub. Anyone can propose a fix to it, such as a clearer description or a field the publisher renamed, as a pull request.

Report a file that differs from the publisher's · How to contribute