Train patronage dataset provides Opal Train Trips by month, operator, contract area and card type. An Opal trip is where an Opal card is used to tap-on and tap-off, including where a single tap-on or tap-off is recorded. All other travel is not included. Peak Train Load Survey 2016 provides estimates of train loads during the AM and PM peak periods - derived from a survey held on Tuesdays, Wednesdays and Thursdays from 1 March 2016 to 17 March 2016. Since the introduction of Opal, this has been replaced by Peak Train Load Estimates from 2017 using the Rail Opal Assignment Model (ROAM). Peak Train Estimates use data extracted from the Rail Opal Assignment Model (ROAM). This model assigns Opal journeys to services based on the rail daily working timetable and train punctuality data. The customer load is aggregated to train services and assigned to rail lines. Train station entries and exits dataset is based on the average of three day sample, representing 'a typical day' of customer entries and exits at each train station.

This dataset contains a consolidated view of Official Utilisation figures across all transport modes (train, metro, bus, ferry and light rail). Opal daily tap-on/tap-off data is aggregated to a total monthly figure representing the estimated number of trips across all transport modes. Starting July 1, 2024, the methodology for calculating trip numbers for individual lines and operators will change to more accurately reflect the services our passengers use within the transport network. This new approach will apply to trains, metros, light rail, and ferries, and will soon be extended to buses. Aggregations between line, agency, and mode levels will no longer be valid, as a passenger may use multiple lines on a single trip. Trip numbers at the line, operator, or mode level should be used as reported, without further combinations. The dataset includes reports based on both the new and old methodologies, with a transition to the new method taking place over the coming months. As a result of this change, caution should be exercised when analysing longer trends that utilise both datasets. More information on NRT ROAM can be accessed here

Ferry Patronage dataset has Opal ferry trips by month, operator, contract area and card type. An Opal trip is where an Opal card is used to tap-on and tap-off, including where a single tap-on or tap-off is recorded. This includes contactless payments. All other travel is not included.

Peak train load estimates use data extracted from the Rail Opal Assignment Model (ROAM). This model assigns Opal journeys to services based on the rail daily working timetable and train punctuality data. The customer load is aggregated to train services and assigned to rail lines.

This dataset provides results data from the Fare Compliance Survey Results reports from November 2012 to the latest report (the surveys were not conducted in 2020 due to Covid). The fare compliance survey is conducted twice yearly in May and November, and is designed to measure the incidence of non-compliance and associated revenue loss across the public transport network. A report from each survey is also published on: https://www.transport.nsw.gov.au/news-and-events/reports-and-publication....

This dataset contains Official Light Rail Utilisation figures. Opal tap-on/tap-off data (representing an individual entering and exiting a Light Rail station), is aggregated to a total monthly figure representing the estimated number of trips. Starting July 1, 2024, the methodology for calculating trip numbers for individual lines and operators will change to more accurately reflect the services our passengers use within the transport network. This new approach will apply to trains, metros, light rail, and ferries, and will soon be extended to buses. Aggregations between line, agency, and mode levels will no longer be valid, as a passenger may use multiple lines on a single trip. Trip numbers at the line, operator, or mode level should be used as reported, without further combinations. The dataset includes reports based on both the new and old methodologies, with a transition to the new method taking place over the coming months. As a result of this change, caution should be exercised when analysing longer trends that utilise both datasets. More information on NRT ROAM can be accessed here Caution School Student travel using concessional Opal cards is included. However this may be underrepresented, due to inconsistent tap-on/tap-off behaviour by students at light rail stations Magnetic Stripe Ticketing (MST – paper tickets) data was also available in July 2016. MST patronage data for July is available here Opal data may be subject to minor revision for the two months following upload Data is static at a point in time, and may not match other reports that are real time All non-Opal travel is excluded, for example transport concession entitlement cards, integrated ticketing for major events, and fare non-compliance An Opal Trip is defined as a tap-on/tap-off pair (including where only a single tap-on or tap-off is recorded) A significant portion of the Light Rail line was closed during the months of January 2017 and 2018, resulting in lower number of trips in both months Please note: the data includes Newcastle Light Rail

This dataset provides an indicator of historic rail occupancy for individual rail services from July 2019. Data included in ROAM - Rail Opal Assignment Model - includes Sydney Trains (T1 - T9) and Metro (Metro North West line) services. Note: With the introduction of the new City and Southwest Metro line, Transport is moving to a new Opal Allocation Model to handle the complexity that these new services will bring. The legacy Rail Opal Allocation Model (ROAM) data will be replaced with a new Near Real Time (NRT) ROAM from May 2024.

This dataset provides counts of tap ons and tap offs made on the Opal ticketing system during four non-consecutive weeks in 2020. The Opal tap on and tap off dataset contains 16 CSV files covering four weeks (28 days) of Opal data across the four public transport modes. Privacy is the utmost priority for all Transport for NSW Open Data and there is no information that can identify any individual in the Open Opal Tap On and Tap Off data. This means that any data that is, or can be, linked to an individual’s Opal card has been removed. This dataset is subject to specific terms and conditions. The CSV files (one for each week) are: Tap on and off time Tap on and off location Tap on and off time and location Origin and destination by travel zone Reported taps are a combination of Opal card and Contactless Transport Payment (CTP) transactions. The tap on and tap off counts are not linked and individual trips cannot be derived using the data. The 28 days are: * Monday 24 Feb 2020 – Sunday 01 March 2020 * Monday 23 March 2020 – Sunday 29 March 2020 * Monday 24 August 2020 – Sunday 30 August 2020 * Monday 16 November 2020 – Sunday 22 November 2020 Release 1 and Release 2 of the data is linked in the Related Content below.

These visualisations feature Opal Trips for all available modes of Public Transport in Sydney CBD. View weekly, monthly and yearly trips from July 2016 onwards.

This dataset provides counts of tap ons and tap offs made on the Opal ticketing system during two non-consecutive weeks in 2016. The Opal tap on and tap off dataset contains six CSV files covering two weeks (14 days) of Opal data across the four public transport modes. Privacy is the utmost priority for all Transport for NSW Open Data and there is no information that can identify any individual in the Open Opal Tap On and Tap Off data. This means that any data that is, or can be, linked to an individual’s Opal card has been removed. This dataset is subject to specific terms and conditions There are three CSV files per week, and these provide a privacy-protected count of taps against: Time – binned to 15 minutes by tap (tap on or tap off), by date and by mode Location– by tap (tap on or tap off), by date and by mode Time with location – binned to 15 minutes, by tap (tap on or tap off), by date and by mode The tap on and tap off counts are not linked and individual trips cannot be derived using the data. The two weeks of Opal data are: 25 July to 31 July 2016 (before paper ticket retirement – paper ticket data is not included in the dataset) 8 August to 14 August 2016 (after paper ticket retirement).