Skip to main content

Farecard Transactions

The Farecard Transactions dataset provides detailed information on entry and exit transactions for public trains and buses. This dataset is maintained by the Land Transport Authority.

Dataset Update Frequency​

DatasetUpdate Frequency
Farecard TransactionsDaily

General Guidelines​

  • Agencies should seek official PT ridership numbers from Land Transport Authority (LTA) for any reporting purposes (other than for their internal studies). PT ridership refers to the number of rides that are made by passengers on public buses, MRT and LRT lines. It is a statistic that is estimated by considering the lines taken within the rail system and the number of boarding events on bus services. The methodology used by Agencies to compute ridership would most likely differ from LTA’s methodology. For example, Agencies may count one entry-exit record as 1 commuter ride . However for LTA’s publicly released and officially reported ridership statistics, they compute PT ridership by considering the lines taken in rail system (i.e. did commuter take more than one rail line between any entry and exit). Hence the ridership associated to a single entry-exit record could be more than 1 commuter ride.

  • The Bus registration number data field (in alphanumeric format) is only available from 18-May-2017. As a physical bus may be moved from one bus service number to another, there may be rare instances (about 0.01%) where the BUS_REGISTER_NUM are NULL values.

  • Due to SG50 celebration on 09-Aug-2015, there was free travel on public buses and trains (no tap-in and tap-out required). This resulted in low no. of farecard transaction records on that day.

  • Due to the nature of how location/positioning data is collected, bus stop sequences may not always be in order. This issue affects a very small number of records per day (less than 0.01%).

  • Due to the nature of how sensor data is collected, the following may exist for a small no. of records per day:

    • Exit Date Time field earlier than Entry Date Time field
    • Entries with same crd_num and entry_dt_tm but dest_loc, orig_loc and/or exit_dt_tm is different.
    • Entries with same crd_num, entry_dt_tm, dest_loc and orig_loc but different exit_dt_tm.
    • Entries with same crd_num, entry_dt_tm but different orig_loc. For such entries, one entry has null dest_loc and exit_dt_tm while the other set has non-null dest_loc and exit_dt_tm.

Hashed Fields​

The crd_num (Card Number) and bus_reg_num (Bus Registration Number / Plate Number) fields are hashed by LTA and/or its service provider(s). The hashing algorithm and salt are owned and managed by LTA, not TCS / DataHive. This means TCS / Datahive does not have a raw identifiable CAN_ID in the Card Number field, nor can we it be recovered by TCS / Datahive from the hash.

Agencies with queries on the CAN_ID should inquire direclty with LTA admins: SEET_Qi_Hao@lta.gov.sg or Jolene_TER@lta.gov.sg.

Fields​

This segment covers a short description and domain-specific information of each field.

Payment Mode​

  • CSC: Contactless SmartCard (includes EZ-Link, SimplyGO Bank cards, etc.)
  • Pass: Includes concessionary passes, monthly passes, etc.
  • Cash
  • Standard Ticket

Commuter Category​

The Commuter Category is NULL when the Payment Mode is Standard Ticket.

  • Child
  • Student
  • Adult
  • Senior Citizen
  • WTCS: Workfare Transport Concession Card
  • PWD: Persons with Disabilities Concession Card