# Victoria Road Crash Data (Australia) - Crashes & Hotspots (`mollydancer/victoria-road-crash-data`) Actor

Every police-reported road crash in Victoria, Australia since 2012: severity, location, speed zone, road users and vehicles. Search by council, road, radius or date, or find crash hotspots. Official open data (CC BY 4.0), updated monthly.

- **URL**: https://apify.com/mollydancer/victoria-road-crash-data.md
- **Developed by:** [MollyDancer](https://apify.com/mollydancer) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 crash records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Victoria Road Crash Data (Australia) - Crashes & Hotspots

Search **every police-reported road crash in Victoria, Australia since 2012** (over 200,000 crashes) and get clean, ready-to-use records. Each record has the date and time, severity, what happened, road, council, speed zone, light conditions, exact map position, casualties, and who was involved: motorcyclists, pillion passengers, pedestrians, cyclists, young and older drivers, trucks, trams and buses.

Or switch to **Summary mode** to get crash and casualty totals by council, road, year, month, speed zone, day of week or hour of day. You can also find **crash hotspots**: the worst intersections and road sections, each with a map link.

**Always up to date:** each run fetches the latest official file from the Victorian Department of Transport and Planning, which updates it monthly. If the government site is unavailable, the Actor uses the copy built into it, so your run still works.

### What you can do with it

- **Road safety consultants and councils:** rank the worst intersections in a council area, track trends by year and compare speed zones.
- **Fleet and logistics safety managers:** find heavy vehicle crash hotspots on your routes.
- **Driver and rider training schools:** show learners real crash patterns for motorcycles, young drivers, night driving and wet roads.
- **Insurers and analysts:** measure crash frequency and severity by area, road type and time of day.
- **Lawyers, journalists and researchers:** pull consistent, citable crash records without spreadsheets.
- **Property buyers and developers:** check crash history within a radius of a site.
- **AI agents:** works through the Apify MCP server, so an assistant can answer questions like "where are the worst motorcycle crash spots in Wyndham?"

### Data coverage

| | |
|---|---|
| Area | All of Victoria, Australia (all councils and alpine resorts) |
| Period | January 2012 – most recent month published (currently March 2026) |
| Volume | About 15,000 injury crashes per year (202,000+ in total) |
| Updates | Monthly, by the Department of Transport and Planning, with a delay of about 7 months |

⚠️ **The most recent months are incomplete.** The Department keeps adding crashes for months afterwards, so treat roughly the last 6–9 months as partial. Recent fatal crash data is provisional. Every run's `OUTPUT` record shows the exact coverage period and which data source was used.

**Privacy:** the source data has **no names, number plates or personal details**, only counts of people by type, plus broad age groups.

### Input examples

**Motorcycle crashes in Wyndham since 2020, most severe first**

```json
{
  "councils": ["Wyndham"],
  "roadUsers": ["motorcyclist"],
  "dateFrom": "2020-01-01",
  "sortBy": "severity"
}
```

**Top 20 crash hotspots in Casey, with at least 5 crashes each**

```json
{
  "outputMode": "summary",
  "summaryGroupBy": "hotspot",
  "councils": ["Casey"],
  "minCrashesPerGroup": 5,
  "maxResults": 20
}
```

**All crashes within 500 m of a site, nearest first**

```json
{
  "nearLatitude": -37.9001,
  "nearLongitude": 144.6610,
  "radiusKm": 0.5
}
```

**Pedestrian crashes at night in 40–50 km/h zones, by year**

```json
{
  "outputMode": "summary",
  "summaryGroupBy": "year",
  "roadUsers": ["pedestrian"],
  "hourFrom": 19,
  "hourTo": 5,
  "speedZones": ["40", "50"]
}
```

#### Filters

`councils`, `roadContains`, `nearLatitude` + `nearLongitude` + `radiusKm`, `dateFrom`, `dateTo`, `daysOfWeek`, `hourFrom`, `hourTo` (overnight windows work), `severities`, `minFatalities`, `roadUsers` (motorcyclist, pillion, pedestrian, bicyclist, heavyVehicle, publicTransport, youngDriver, olderDriver, olderPedestrian, child), `crashTypes`, `speedZones`, `lightConditions`, `sortBy`, `maxResults`.

Council names work either way: official or short form, such as "Greater Geelong" or "Geelong". "Moreland" and "Merri-bek" are treated as the same council.

### Output examples

**Crash row** (shortened)

```json
{
  "crashId": "T20250033871",
  "date": "2025-12-24",
  "time": "14:35",
  "dayOfWeek": "Wednesday",
  "crashType": "Vehicle overturned (no collision)",
  "severity": "Serious injury",
  "speedZone": 60,
  "roadGeometry": "Cross intersection",
  "road": "Dunnings Road -Shaftsbury Boulevard",
  "council": "Wyndham",
  "latitude": -37.88666,
  "longitude": 144.75,
  "seriousInjuries": 1,
  "motorcyclists": 1,
  "motorcycles": 1,
  "mapUrl": "https://www.google.com/maps?q=-37.88666,144.75"
}
```

Each crash also includes the crash type code and its description, light conditions, road class, divided road, run-off-road, police attended, region, urbanisation, and counts of drivers, passengers, pedestrians, cyclists, pillion passengers, young drivers (18–25), older drivers (75+), older pedestrians (65+), child and teen pedestrians or cyclists, and vehicles by type.

**Hotspot row**

```json
{
  "group": "Sayers Road, Forsyth Road (Wyndham)",
  "crashes": 27,
  "fatalCrashes": 0,
  "seriousInjuryCrashes": 6,
  "seriousInjuries": 6,
  "otherInjuries": 28,
  "fatalOrSeriousShare": 0.222,
  "crashesInvolvingYoungDrivers": 10,
  "firstCrashDate": "2021-10-17",
  "lastCrashDate": "2025-12-08",
  "latitude": -37.852702,
  "longitude": 144.731057,
  "mapUrl": "https://www.google.com/maps?q=-37.852702,144.731057",
  "mostCommonSpeedZone": 60
}
```

Hotspots are built around the busiest locations instead of a fixed grid, so an intersection's crashes are never split between two squares. Choose the hotspot size with `hotspotSizeMetres`; the default of 250 m suits intersections.

Download results as JSON, CSV, Excel or HTML, or connect them to Google Sheets, Make, Zapier or your own code through the Apify API.

### Pricing

Pay only for what you get:

- **$3 per 1,000 crash records** returned
- **$0.03 per summary row** (a council, road, year or hotspot)

Examples: the top 20 hotspots in a council cost $0.60. Yearly totals since 2012 (15 rows) cost $0.45. Set a maximum cost per run in Apify Console and the Actor stops at exactly that amount. Users on Apify's free plan get a preview (the first 25 crashes or 5 summary rows).

### Good to know

- Crashes are police-reported injury crashes. Property-damage-only crashes generally aren't included.
- Times are often rounded by police at the scene.
- About 0.6% of crashes have no map position; they're left out of radius searches and hotspots but included elsewhere.
- Road names come straight from the source and occasionally include ramp or intersection descriptions.

### Data source and licence

Source: Department of Transport and Planning (Victoria), [*Victoria Road Crash Data*](https://opendata.transport.vic.gov.au/dataset/victoria-road-crash-data), licensed under the [Creative Commons Attribution 4.0 International licence](https://creativecommons.org/licenses/by/4.0/). This Actor cleans and restructures the data: readable labels, standardised council names, speed zones as numbers, hotspots and summaries. Every row carries an attribution line.

This Actor is independent and is **not affiliated with or endorsed by** the Department of Transport and Planning or the Victorian Government. The Department makes no claim as to the accuracy or currency of the data. Check important findings against official sources.

# Actor input Schema

## `outputMode` (type: `string`):

Individual crashes (one row per crash), or a summary (one row per council, road, year, hotspot etc.) with crash and casualty counts.

## `summaryGroupBy` (type: `string`):

Only used in summary mode. 'Hotspot' groups crashes into small map squares and ranks the worst locations.

## `hotspotSizeMetres` (type: `integer`):

Width of each hotspot map square. 250 m suits intersections and short road sections.

## `minCrashesPerGroup` (type: `integer`):

Summary mode only: leave out groups with fewer crashes than this (handy for hotspots).

## `councils` (type: `array`):

Council (local government area) names, e.g. Wyndham, Casey, Greater Geelong, Melbourne. Leave empty for all of Victoria.

## `roadContains` (type: `string`):

Text to match in the road name, e.g. 'Princes' or 'Hoppers Lane'.

## `nearLatitude` (type: `number`):

Find crashes within a radius of a point. Example: -37.9001 (Werribee). Use with Near longitude.

## `nearLongitude` (type: `number`):

Example: 144.6610 (Werribee). Use with Near latitude.

## `radiusKm` (type: `number`):

Used with Near latitude / longitude.

## `dateFrom` (type: `string`):

YYYY-MM-DD

## `dateTo` (type: `string`):

YYYY-MM-DD (inclusive)

## `daysOfWeek` (type: `array`):

Leave empty for every day.

## `hourFrom` (type: `integer`):

Time-of-day window. Overnight works too, e.g. from 22 to 4.

## `hourTo` (type: `integer`):

Inclusive, e.g. 9 means up to 9:59.

## `severities` (type: `array`):

Leave empty for all crashes.

## `minFatalities` (type: `integer`):

e.g. 2 for multi-fatality crashes.

## `roadUsers` (type: `array`):

Only crashes that involve ALL of the selected road users.

## `crashTypes` (type: `array`):

Leave empty for all types.

## `speedZones` (type: `array`):

Leave empty for all speed zones.

## `lightConditions` (type: `array`):

Leave empty for all.

## `sortBy` (type: `string`):

Crashes: newest, oldest, most severe, or nearest (radius searches sort nearest first by default). Summaries: 'Most severe' ranks by fatal then serious crashes instead of total crashes.

## `maxResults` (type: `integer`):

Stop after this many rows. You are charged per row returned.

## `useBundledData` (type: `boolean`):

By default each run fetches the latest official file. Tick to skip that and use the copy built into the Actor (slightly faster, may be a month or two older).

## Actor input object example

```json
{
  "outputMode": "crashes",
  "summaryGroupBy": "council",
  "hotspotSizeMetres": 250,
  "radiusKm": 1,
  "maxResults": 100,
  "useBundledData": false
}
```

# Actor output Schema

## `crashes` (type: `string`):

One row per crash (when 'Individual crashes' is selected).

## `summary` (type: `string`):

One row per council, road, hotspot, year etc. (when 'Summary / hotspots' is selected).

## `runSummary` (type: `string`):

Matching crashes, rows returned, data source and coverage period.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("mollydancer/victoria-road-crash-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxResults": 100 }

# Run the Actor and wait for it to finish
run = client.actor("mollydancer/victoria-road-crash-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxResults": 100
}' |
apify call mollydancer/victoria-road-crash-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mollydancer/victoria-road-crash-data"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/cXPNnbdjUoOV6iXUA/builds/tH7hS5quJfDVxHgki/openapi.json
