A rail journey involving Bukit Mertajam can appear in a northern-network data table without telling you how crowded the next train will be. The useful question is narrower: how many recorded journeys shared a particular origin, destination and transaction hour? This guide reads the official Komuter Utara catalogue, checked on 20 October 2026, for mainland Penang readers who want to understand that distinction.

Read the row as a journey record

The official catalogue says the dataset is generated from KTMB’s integrated ticketing transactions. Its fields separate date, time, origin, destination and ridership. Ridership is defined as journeys and is not necessarily a count of different people. A person making more than one journey should therefore not automatically become more than one distinct resident in your interpretation.

For a mainland station, keep the direction explicit. An origin at Bukit Mertajam and a destination elsewhere describes a different flow from the reverse pairing. Combining both directions answers a different question; it should be labelled rather than silently treated as the original row.

The hour is a bucket, not a departure

The time field groups transactions within an hour. The catalogue’s 09:00 example covers 09:00 through 09:59, rather than rounding observations to the nearest hour. It is not an advertised 09:00 train.

A useful worksheet therefore places the selected reporting date and the hourly interval next to the station pair. Keep a separate column for any timetable information obtained from the operator. This prevents a chart label from turning into an invented departure time or a promise about the service a passenger will catch.

What a Penang comparison needs

If you compare a weekday with a weekend, use the same direction and comparable hours. If you compare two stations, explain whether the figures cover journeys leaving the stations, arriving at them, or both. These are proposed analytical choices, not findings calculated for this article.

Do not infer a train’s carriage occupancy from an origin-destination total. That conclusion would require information about which service carried the journeys, its capacity, intermediate movements and the relevant observation method. A mainland station also belongs to a network extending beyond Penang, so the table is not a census of Penang residents.

Check the file and reporting cutoff

The page read for this guide displayed data through 5 October 2026. That cached reporting cutoff is different from this article’s source-check date. No complete download or new aggregate was calculated here. The catalogue warns that the full multi-year data exceeds an ordinary spreadsheet’s row limit and directs users to downloadable files; its example OpenAPI route is unavailable for this dataset.

A practical conclusion

Use this dataset for a clearly defined movement question, then use current operator information for an actual trip. Keep the reporting period, direction and counting unit visible in every chart. That makes a small rail-data comparison useful without turning it into an unsupported travel forecast. Source: official Komuter Utara catalogue.

Related Penang service guide: Match a Penang ferry journey to the right terminal and onward leg.