IMPORTANT: This link is no longer updated. To access MBTA Rapid Transit Events 2024 data, please go to MBTA Rapid Transit Events 2024. Rapid Transit Events data is now sourced from Lightweight Application for Measuring Performance (LAMP). To learn more about LAMP, please visit LAMP website.This file contains the arrival and departure events for rapid transit lines for 2024. It includes all heavy rail and light rail rapid transit lines. These events are used to calculate travel times, dwell times, and headways. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date. Data Dictionary:

NameDescriptionData TypeExampleservice_dateDate for which events should be returned.Date2024-01-01route_idGTFS-compatible route for which events should be returned.StringOrangetrip_idGTFS-compatible trip for which events should be returned.String461_1direction_idGTFS-compatible direction for which events should be returned.Integer0stop_idGTFS-compatible stop for which ridership should be returned.Stringplace-wlstastop_sequenceGTFS-compatible order of stops on a route for which events should be returned.Integer590vehicle_idProperty of “events”. The identifier for the vehicle performing the trip for which events are returned.StringR-545A9644vehicle_labelProperty of “events”. Human-readable, publicly visible identifier for the vehicle.String3830-3652event_typeThe type of event: ‘ARR’ for arrival, ‘DEP’ for departure, ‘PRA’ for predicted arrival, and ‘PRD’ for predicted departure. PRA and PRD events occur when the Performance system is relatively sure that a train actually made the indicated movement at the indicated station, but the system did not observe an "actual" event from the realtime system. In that case, we use the last available prediction for the given event as a reasonable proxy. We often lack actual ARR events at terminals because the realtime system is designed for tracking trains that passengers want to board, not necessarily trains that have already arrived at a terminal station. The instant a train arrives at a terminal station (e.g. arriving northbound at Oak Grove), the MBTA-performance system may no longer be able to track its location. In some cases, we are not able to fill in a PRA event at all, so some types of analysis are less accurate at terminals. Depending on your objectives, you may wish to use the second-to-last station as a proxyStringDEPevent_timeThe time of the event, in epoch time.Integer1546349755event_time_secThe time of the event, in seconds after midnight.Integer30955MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

For each route, day, and peak/offpeak time range, this file provides numerators separate from denominators, for flexibility in combining routes, peak/offpeak, before calculating reliability metrics. It is ONLY valid to aggregate numerator and denominator values within a single mode_type. If you attempt to aggregate Reliability performance between Bus and Commuter Rail, for example, you will NOT get meaningful results. For definitions of the metrics, see the MBTA Performance Dashboard (high-level definitions) and the MBTA Service Delivery Policy (detailed definitions). Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date.Note:- on peak_offpeak_ind: rows labeled PEAK will only appear for weekdays.- contracted bus routes (i.e 712/713) are not included. - for the Commuter Rail lines with branches, the reliability metric is included for each branch.Due to data collection issues, the following dates and/or lines are missing from this data set:Oct 10-11, 2015June 1-3, 2018MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This file contains the headways, or time between the departure time of the current trip and the departure time of the previous trip from the same stop, for rapid transit vehicles. It includes all heavy rail and light rail rapid transit lines. For Red and Green lines, both trunk (e.g. all Green line trains) and branch (e.g. Green-B trains) headways are included. For lines without branches (e.g. Blue line), branch route ID and branch headway will be NULL. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date.

Data Dictionary

Each row represents a unique service_date-trip_id-stop_id pair for rail service.

field name

type

description

source

example

service_date

date

equivalent to GTFS-RT start_date value in Trip Descriptor as date instead of string

GTFS-RT

2024-01-01

route_id

string

equivalent to GTFS-RT route_id value in Trip Descriptor

GTFS-RT

Orange

trunk_route_id

string

line if multiple routes exist on line, otherwise route_id, e.g. Green for Green-B route, Blue for Blue route

GTFS-RT

Green

branch_route_id

string

equivalent to GTFS-RT route_id value in Trip Descriptor for lines with multiple routes, NULL if line has single route, e.g. Green-B for Green-B route, NULL for Blue route_id.

GTFS-RT

Green-B

trip_id

string

equivalent to GTFS-RT trip_id value in Trip Descriptor

GTFS-RT

62248746

direction_id

int

equivalent to GTFS-RT direction_id value in Trip Descriptor

GTFS-RT

0

direction

string

equivalent to GTFS direction value from directions.txt for route_id-direction_id pair

GTFS

East

parent_station

string

the parent_station associated with the stop_id from stops.txt

GTFS

place-babck

stop_id

string

equivalent to GTFS-RT stop_id value in VehiclePosition

GTFS-RT

70560

stop_name

string

equivalent to GTFS stop_name from stops.txt for stop_id

GTFS

Babcock Street

stop_departure_datetime

datetime

earliest "IN_TRANSIT_TO" OR "INCOMING_AT" status timestamp for a trip-stop pair from GTFS-RT VehiclePosition as an Eastern datetime.

GTFS-RT

11/1/2023 5:24:51 AM

stop_departure_sec

int

stop_departure_datetime as seconds after midnight

LAMP Calculated

20,517

headway_branch_seconds

int

seconds between consecutive vehicles departing parent_station on branch_route_id

LAMP Calculated

1,387

headway_trunk_seconds

int

seconds between consecutive vehicles departing parent_station on trunk_route_id

LAMP Calculated

311

Changes to the data:

Rapid Transit Events data is now sourced from Lightweight Application for Measuring Performance (LAMP). To learn more about LAMP, please visit LAMP Website.

The data changed as follows:

Trunk_route_id field is added.

Branch_route_id field is added.

Trip_id field is added.

Direction field is added.

Destination is now replaced conceptually by branch_route_id.

Parent_station field is added.

Stop_name field is added.

Start_time_sec field is no longer included (if needed can be calculated as stop_departure_seconds - headway_*_seconds)

Stop_departure_datetime field is added.

End_time_sec is now stop_departure_sec.

Headway_time_sec is changed from long to wide and is now headway_branch_seconds and headway_trunk_seconds.

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This file contains detailed boarding, alighting, and load data for bus. It contains the averages per trip, season, route/line, direction, stop, day type, and time period. Data is available for Fall seasons from 2016 through 2023.Data Dictionary:NameDescriptionData TypeExampleseasonSeason and year for which ridership should be returned.StringFall 2017route_idGTFS-compatible route for which ridership should be returned.String34Eroute_variantGTFS compatible route pattern id that identifies the variation from the typical trip taken by the vehicle. Indicates the route, variant number, and direction of trip.String34E-6-1direction_idGTFS-compatible direction for which ridership should be returned.Integer0trip_start_time24-hour time at which the one-way trip began. Trips starting after 11:59 PM are represented as 24:00 plus their 24-hour time. For example, a trip starting at 1:30 AM will be 25:30:00.Time05:15:00day_type_idShorthand for day identifier.Stringday_type_01day_type_nameText description of the id. Weekday, Saturday, or Sunday; holidays are excluded from the data.StringWeekdaystop_nameGTFS-compatible stop name for which ridership should be returned.StringWASHINGTON ST OPP RUGGLES STstop_idGTFS-compatible stop for which ridership should be returned.String1stop_sequenceThe ordinal identifier of the stop on the particular trip.Integer9average_boardingsThe average count of passengers getting on vehicles.Double435.6average_alightingsThe average count of passengers leaving vehicles.Double65.4average_loadThe average number of passengers on the vehicle upon leaving a stop, summed by the aggregated fields; represented as cumulative average load out.Double17.8sample_sizeThe number of trips scheduled at the start time used to calculate the average boardings, alightings, and loads.Integer18MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

It includes all heavy rail and light rail rapid transit lines. These travel times are calculated from the departure time at the origin stop to the arrival time at the destination stop. Due to track circuit or other data issues, data is not guaranteed to be complete for any origin-destination pair or date.Data Dictionary:NameDescriptionData TypeExampleservice_dateDate for which travel times should be returned.Date43830route_idGTFS-compatible route for which travel times should be returned.StringOrangedirection_idGTFS-compatible direction for which travel times should be returned.Integer0from_stop_idGTFS-compatible stop representing the origin stop in a pair.String70205to_stop_idGTFS-compatible stop representing the destination stop in a pair.String70154start_time_secProperty of “Travel Times”. Expressed in "seconds after midnight." The time associated with the departure event of the vehicle from the origin stop of the pair.Integer45763end_time_secProperty of “Travel Times”. Expressed in "seconds after midnight." The time associated with the arrival event of the vehicle to the destination stop of the pair.Integer46411travel_time_secProperty of “Travel Times”. Difference between start_time_sec and end_time_sec. The actual travel time between the origin stop and the destination stop, in seconds.Integer648MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Information and links for developers to work with real-time and static transportation data.

This file contains the travel times between origin and destination pairs on a single line.

It includes all heavy rail and light rail rapid transit lines. These travel times are calculated from the departure time at the from_stop to the arrival time at the to_stop. Due to track circuit or other data issues, data is not guaranteed to be complete for any origin-destination pair or date.

Data Dictionary

Each row represents a unique service_date-trip_id-from_stop_id-to_stop_id unit for rail service.

field name

type

description

source

example

service_date

date

equivalent to GTFS-RT start_date value in Trip Descriptor as date instead of string

GTFS-RT

2024-01-01

route_id

string

equivalent to GTFS-RT route_id value in Trip Descriptor

GTFS-RT

Orange

trip_id

string

equivalent to GTFS-RT trip_id value in Trip Descriptor

GTFS-RT

62248746

direction_id

int

equivalent to GTFS-RT direction_id value in Trip Descriptor

GTFS-RT

0

direction

string

equivalent to GTFS direction value from directions.txt for route_id-direction_id pair

GTFS

East

from_parent_station

string

stop_name of the parent_station associated with the stop_id from stops.txt for origin stop.

GTFS

place-amory

from_stop_id

string

equivalent to GTFS-RT stop_id value in VehiclePosition for origin stop.

GTFS-RT

170141

from_stop_name

string

equivalent to GTFS stop_name from stops.txt for destination stop_id.

GTFS

Amory Street

to_parent_station

string

stop_name of the parent_station associated with the stop_id from stops.txt for destination stop.

GTFS

place-babck

to_stop_id

string

equivalent to GTFS-RT stop_id value in VehiclePosition for destination stop.

GTFS-RT

70560

to_stop_name

string

equivalent to GTFS stop_name from stops.txt for origin stop_id.

GTFS

Babcock Street

from_stop_departure_datetime

datetime

earliest "IN_TRANSIT_TO" OR "INCOMING_AT" status timestamp from origin stop (previous stop) from GTFS-RT VehiclePosition as an Eastern datetime.

GTFS-RT

11/1/2023 5:24:51 AM

from_stop_departure_sec

int

from_stop_departure_datetime as seconds after midnight

LAMP Calculated

84912

to_stop_arrival_datetime

datetime

earliest "STOPPED_AT" status timestamp for destination stop from GTFS-RT VehiclePosition or last arrival timestamp from GTFS-RT StopTimeUpdate if VehiclePosition value is not available as an Eastern datetime.

GTFS-RT

11/1/2023 5:25:34 AM

to_stop_arrival_sec

int

to_stop_arrival_datetime as seconds after midnight

LAMP Calculated

84992

travel_time_sec

int

seconds the vehicle spent traveling between origin stop and destination stop on trip.

Calculated for Open Data Portal

80

Changes to the data

Rapid Transit Travel Time data is now sourced from Lightweight Application for Measuring Performance (LAMP). To learn more about LAMP, please visit LAMP website.

The data changed as follows:

Trip_id field is added.

Direction field is added.

From_parent_station field is added.

From_stop_name field is added.

To_parent_station field is added.

To_stop_name field is added.

From_stop_departure_datetime field is added.

To_stop_arrival_datetime field is added.

Start_time_sec is now from_stop_departure_sec.

End_time_sec is now to_stop_arrival_sec.

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

For more information about the MBTA System-Wide Passenger Survey, please see the Rider Census website.FieldData TypeDescriptionaggregation_levelStringLevel of aggregation. One of: Reporting Group, Rapid Transit or Bus Rapid Transit Line, Service Mode, or Systemwide.service_modeStringMBTA service mode. One of: Bus (includes SL4/SL5), Commuter Rail, Ferry, Rapid Transit or Bus Rapid Transit - Blue Line, Rapid Transit or Bus Rapid Transit - Green Line, Rapid Transit or Bus Rapid Transit - Orange Line, Rapid Transit or Bus Rapid Transit - Red Line, Rapid Transit or Bus Rapid Transit - Mattapan Trolley, Rapid Transit or Bus Rapid Transit - Silver Line BRT (includes SL1/SL2/SL3).reporting_groupStringMBTA service reporting group. This field will be at different levels for different MBTA service modes. Generally speaking, heavy rail is summarized to the station or small group of geographically proximate stations, light rail is summarized to the branch, bus is summarized to the route or geographic group of routes, commuter rail is summarized to the line, and ferry is summarized to the mode.measure_groupStringCategory of measure: e.g., Race and Ethnicity, Income.measureStringMeasure: e.g., Race, Hispanic or Latino, Title VI Minority.categoryStringSpecific category for which data is being provided.weighted_percentNumericThe proportion of riders answering a question in the given category.MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This file contains the 178 cities and towns in Massachusetts for which MBTA bus, rapid transit, or commuter rail service is provided. This data is based off of the 2010 census. The legislative intent for some boundaries could not be mapped. Boundaries where that is true are identified in the attribute information. NameDescriptionData TypeExampletownFull name for the MA town or city identification.StringBostontown_idMassGIS Town-ID Code (alphabetical, 1-351)Numeric34sum_acresArea covered by the town or city in acres.Double31304.22sum_squareArea covered by the town or city in square miles.Double48.91 MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Our guide to system data definitions, data collection methods, and data sets. Updated June 2020.Included in this guide:Key Words:System DataVehicle Location DataGeneral Transit Specific Feed (GTFS)Service AreaEvent (rail)Travel Time (rail)Headway (rail)Headway (bus)AlertsStop DistanceDirectionStop SequencePeak HourTime PeriodService DaySeasonHow We Collect System Data:Using Vehicle Location Data for:Using GTFSVehicle Location Data Use CasesReference Table Use CasesMassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Distances, in meters and miles, between stops on MBTA rapid transit lines. This includes the Red Line, Green Line, Blue Line, Orange Line, and Mattapan Trolley.This data is obtained from GTFS. While suitable for the vast majority of applications, small inaccuracies may be present. MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

It includes all heavy rail and light rail rapid transit lines. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date. Data Dictionary:NameDescriptionData TypeExampleservice_dateDate for which headways should be returned.Date2019-12-31route_idGTFS-compatible route for which headways should be returned.StringOrangedirection_idGTFS-compatible direction for which headways should be returned.Integer0stop_idGTFS-compatible stop for which headways should be returned.String70154start_time_secProperty of “Headways”. Expressed in "seconds after midnight." The time associated with the departure event of previous vehicle.Integer45763end_time_secProperty of “Headways”. Expressed in "seconds after midnight." The time associated with the departure event of current vehicle.Integer46411headway_time_secProperty of “Headways”. Difference between start_time_sec and end_time_sec. The actual travel time between the origin stop and the destination stop, in seconds. Red line trunk stops will have two headways for the same southbound train: one dependent on the destination and one independent of the destination.Integer648destinationProperty of “Headways”. Intended destination for the vehicle.StringForest HillsMassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

It includes all heavy rail and light rail rapid transit lines. These events are used to calculate travel times, dwell times, and headways. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date. Data Dictionary:

Name
Description
Data Type
Example


service_date
Date for which events should be returned. 
Date
2019-12-31


route_id
GTFS-compatible route for which events should be returned. 
String
Orange


trip_id
GTFS-compatible trip for which events should be returned. 
String
461_1


direction_id
GTFS-compatible direction for which events should be returned. 
Integer
0


stop_id
 GTFS-compatible stop for which ridership should be returned.
String
place-wlsta


stop_sequence
 GTFS-compatible order of stops on a route for which events should be returned.
Integer
590


vehicle_id
Property of “events”. The identifier for the vehicle performing the trip for which events are returned. 
String
R-545A9644


vehicle_label
Property of “events”. Human-readable, publicly visible identifier for the vehicle. 
String
3830-3652


event_type
The type of event: ‘ARR’ for arrival, ‘DEP’ for departure, ‘PRA’ for predicted arrival, and ‘PRD’ for predicted departure.PRA and PRD events occur when the Performance system is relatively sure that a train actually made the indicated movement at the indicated station, but the system did not observe an "actual" event from the realtime system. In that case, we use the last available prediction for the given event as a reasonable proxy. We often lack actual ARR events at terminals because the realtime system is designed for tracking trains that passengers want to board, not necessarily trains that have already arrived at a terminal station. The instant a train arrives at a terminal station (e.g. arriving northbound at Oak Grove), the MBTA-performance system may no longer be able to track its location. In some cases, we are not able to fill in a PRA event at all, so some types of analysis are less accurate at terminals. Depending on your objectives, you may wish to use the second-to-last station as a proxy
String
DEP


event_time
The time of the event, in epoch time. 
Integer
1546349755


event_time_sec
The time of the event, in seconds after midnight. 
Integer
30955

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Our guide to ridership definitions, data collection methods, and data sets. Updated June 2020.Included in this guide:How We Calculate Ridership:Automatic Passenger Counters (APC)Automated Fare Collection (AFC)Manual countsKey Words:FlowLoadRidershipStation EntriesPeak HourService DayTime PeriodSeasonSuggested Use CasesAverage Weekday Gated Station Entries FY19MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This file contains detailed ridership and flow data for heavy rail and light rail. It contains the average ridership per season, route/line, direction, stop, day type, and time period. Data is available for Fall 2017, Fall 2018, and Fall 2019.Due to track circuit issues, the Fall 2018 season for heavy and light rail only includes the month of September.Due to track servicing and shuttling, weekend volume for the Orange line between Forest Hills and Ruggles is underestimated during the Fall 2018 season.Due to construction, volume for the Red line at Wollaston is underestimated during the Fall 2018 season.Data Dictionary:

Name
Description
Data Type
Example


mode
GTFS-compatible mode of transportation for which ridership should be returned. 
Integer
1


season
Season and year for which ridership should be returned. 
String
Fall 2017


route_id
Route for which ridership should be returned. 
String
Red


route_name
Description of route.
String
Red Line


direction_id
GTFS-compatible direction for which ridership should be returned. 
Integer
0


day_type_id
Shorthand for day identifier. 
String
day_type_01


day_type_name
Text description of the id. Weekday, Saturday, or Sunday; holidays are excluded from the data. 
String
Weekday


time_period_id
Shorthand for time period identifier, per our Service Delivery Policy. 
String
time_period_03


time_period_name
Aggregated periods of varying lengths to represent different levels of service provided. 
String
AM_RUSH


stop_name
 GTFS-compatible stop name for which ridership should be returned.
String
Wollaston


parent_station
 GTFS-compatible stop for which ridership should be returned.
String
place-wlsta


total_ons
The count of passengers boarding vehicles, summed by the aggregated fields.
Integer
1491


total_offs
The count of passengers alighting vehicles, summed by the aggregated fields.

Integer
7990


number_service_days
Number of non-holiday service days in the season based on day type.
Integer
19


average_ons
Represents the ons on a typical service day within the aggregated fields. Calculated by total_ons/number_service_days.

Double
435.6


average_offs
Represents the offs on a typical service day within the aggregated fields. Calculated by total_offs/number_service_days. 
Double
65.4


average_flow
The total number of passengers traveling through the rail system between stations within the aggregated time period, averaged to represent the typical weekday, saturday, or sunday.
Integer
21

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

Data Dictionary:NameDescriptionData TypeExampleSeasonSeason and year of when passenger comfort was calculatedStringFall 2019sdp_modeMode of service (either bus or heavy rail)StringBusroute_idGTFS-compatible routeString10day_typeDay type of service (weekday, saturday, sunday). Holidays are excluded. StringWeekdaypassenger_minutes_totalThe estimated number of total passenger minutes spent inside a vehicle for a given routeDouble12946564.4sdp_uncomfortable_minutes_totalThe estimated number of passenger minutes spent in crowded/uncomfortable conditions (defined by the SDP) inside a vehicle for a given routeDouble1769978.838crowdingsdp_uncomfortable_minutes_total/passenger_minutes_total; time spent in uncomfortable conditonsDouble0.14comfort_measure1 - crowding; time spent in comfortable conditionsDouble0.86 MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

It includes all heavy rail and light rail rapid transit lines. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date.Due to data collection issues, the following dates and/or lines are missing from this data set:March 23, 2020 Mattapan High Speed Line. Data Dictionary:

Name
Description
Data Type
Example


service_date
Date for which headways should be returned. 
Date
2020-12-31


route_id
GTFS-compatible route for which headways should be returned. 
String
Orange


direction_id
GTFS-compatible direction for which headways should be returned. 
Integer
0


stop_id
GTFS-compatible stop for which headways should be returned.
String
70154


start_time_sec
Property of “Headway”. Expressed in "seconds after midnight." The time associated with the departure event of previous vehicle.
Integer
45763


end_time_sec
Property of “Headway”. Expressed in "seconds after midnight." The time associated with the departure event of current vehicle.
Integer
46411


headway_time_sec
Property of “Headway”. Difference between start_time_sec and end_time_sec. The actual headway between two trains with the same destination, in seconds. Red line trunk stops will have two headways for the same southbound train: one dependent on the destination and one independent of the destination.
Integer
648


destination
Property of “Headway”. Intended destination for the vehicle.
String
Forest Hills

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

It includes all heavy rail and light rail rapid transit lines. Due to track circuit or other data issues, data is not guaranteed to be complete for any stop or date.Due to data collection issues, the following dates and/or lines are missing from this data set:January 21, 2017 Blue LineJune 4, 2017 Mattapan High Speed LineOctober 22, 2017 Mattapan High Speed LineFebruary 8 - March 2, 2017 All Green Line branchesMattapan High Speed Line data available beginning May 30, 2017.Data Dictionary:

Name
Description
Data Type
Example


service_date
Date for which headways should be returned. 
Date
2019-12-31


route_id
GTFS-compatible route for which headways should be returned. 
String
Orange


direction_id
GTFS-compatible direction for which headways should be returned. 
Integer
0


stop_id
GTFS-compatible stop for which headways should be returned.
String
70154


start_time_sec
Property of “Headways”. Expressed in "seconds after midnight." The time associated with the departure event of previous vehicle.
Integer
45763


end_time_sec
Property of “Headways”. Expressed in "seconds after midnight." The time associated with the departure event of current vehicle.
Integer
46411


headway_time_sec
Property of “Headways”. Difference between start_time_sec and end_time_sec. The actual headway between two trains with the same destination, in seconds. Red line trunk stops will have two headways for the same southbound train: one dependent on the destination and one independent of the destination.
Integer
648


destination
Property of “Headways”. Intended destination for the vehicle.
String
Forest Hills

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

This map service contains layers from the stops, shapes, and facilities files from the MBTA GTFS.MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.