Data source
All schedules come from the static GTFS (General Transit Feed Specification) feed that C-TRAN publishes for trip planners. GTFS is a set of plain-text tables; this site uses five of them:
stops.txtfor stop names, IDs, coordinates and transit center baystrips.txtfor each trip's route, direction, destination sign and service IDstop_times.txtfor the scheduled time of every trip at every stopcalendar.txtandcalendar_dates.txtfor the dates each service ID operates
The feed used here covers dates from September 13, 2026 to January 9, 2027. This site shows the schedule pattern in effect from October 18, 2026 to January 9, 2027. The full specification is published at gtfs.org.
Service days and dates
Each trip in the feed belongs to a service ID, and the calendar files say which service IDs run on each date. This site resolves the active service IDs for every date in the feed, then groups dates by their exact combination of service IDs.
For weekdays, Saturdays and Sundays separately, the most common combination among upcoming dates defines that day's schedule. In the current feed these are 1-WKDY + 1-WKDY/31 for weekdays, 2-SAT + 2-SAT/31 for Saturdays and 3-SUN + 3-SUN/31 for Sundays. The service period runs from the first to the last date that uses one of these combinations.
Dates that use another day's combination are treated as holidays on that schedule. Thanksgiving Day (Thursday, November 26, 2026), Christmas Day (Friday, December 25, 2026) and New Year's Day (Friday, January 1, 2027) follow the Sunday schedule. New Year's Eve (Thursday, December 31, 2026) has a special schedule that differs from the regular weekday schedule, including added late-night trips on several routes. That schedule is not shown on this site.
Some dates add an extra service ID on top of the regular weekday schedule. These are shown as special service: Route 899 runs on 11 dates this period and appears on its own route page and on the pages of its stops, with the dates listed. It is not included in weekday totals or expected waits.
What counts as a departure
A departure is a scheduled stop time where a rider can board. Two kinds of stop time are excluded:
- The final stop of each trip, where the bus ends its run and riders only get off.
- Stop times marked drop-off only in the feed (
pickup_type1).
GTFS writes trips after midnight with hours past 24, such as 25:10:00. These stay with the service day they belong to and are shown on the 12-hour clock under hours marked next day. All times are local Pacific Time.
Expected wait
For each stop and service day, this site sorts the departures by time and measures each gap (headway) between one departure and the next, in minutes. The expected wait is:
where h1 to hn are the gaps between consecutive departures. This is the average wait of a rider who arrives at a random moment between the first and last departure of the day without looking at a schedule. A rider is more likely to arrive during a long gap than a short one, because long gaps take up more of the day, and then waits half of that gap on average. Weighting each gap by its own length gives the formula above.
Two consequences follow. First, with perfectly even spacing the expected wait is exactly half the headway: a bus every 30 minutes gives 15 minutes. Second, uneven spacing always makes it longer, even with the same number of buses. Departures from every route at the stop are combined, so the figure describes the wait for the next bus of any route.
A worked example
Suppose a stop has four departures: 7:00, 7:10, 7:40 and 8:00 AM.
| Gap | Headway h (min) | h squared |
|---|---|---|
| 7:00 to 7:10 | 10 | 100 |
| 7:10 to 7:40 | 30 | 900 |
| 7:40 to 8:00 | 20 | 400 |
| Total | 60 | 1,400 |
The expected wait is 1,400 / (2 x 60) = 11.7 minutes. The average headway is 20 minutes, and half of that is 10 minutes; the extra 1.7 minutes comes from the uneven spacing.
Other measures
- Departures count every departure from the stop on that service day.
- First bus and last bus are the earliest and latest departures; a last bus after midnight is marked next day.
- Longest gap is the largest headway between consecutive departures.
- Rank orders all stops with the same service day by expected wait, with 1 for the shortest. The bar under the expected wait shows where the stop falls between the shortest and longest waits.
- Route frequency is the median gap between departures at the route's busiest stop in its busier direction. Routes with fewer than 10 trips in a direction are labeled limited, because a median across a few peak trips would mislead.
- Route timetables show times at timepoints (stop times with
timepoint1). When trips in one direction follow different stop patterns, their stops are merged into one sequence. - Nearby stops are the closest stops by straight-line distance between coordinates, not walking distance.
- Next scheduled departures uses the current date and time in Pacific Time, the service calendar and the times on the page. It includes late trips from the previous service day that run after midnight.
Verification
The weekday expected waits were checked against an independent implementation of the same method run on the same feed. All 885 weekday stop values agree to within floating-point rounding. Departure counts, first and last times and route trip totals are computed directly from the feed tables without sampling or estimation.
Limitations
- Scheduled, not observed. The figures describe the timetable. Real buses run early or late, and detours or cancellations are not reflected.
- Random arrival. Expected wait assumes riders arrive without consulting the schedule. Riders who time their arrival wait less, which matters most at stops with long gaps.
- Any route. Expected wait counts every route at a stop. A rider who needs one particular route may wait longer than the figure suggests. Use the route filter on the stop page to see that route alone.
- Service hours only. Waits are measured between the first and last departure. Time outside service hours is not counted.
- Peak-only stops. At stops with a few morning and afternoon trips, the midday gap dominates. Fisher's Landing Transit Center: Bay H, for example, has an expected weekday wait of 262.3 minutes from 5 departures. The number is correct for a random arrival but riders there plan around the listed times.
- Feed accuracy. Stop names, locations and times are shown as published. If something here differs from C-TRAN's official information, the official information takes precedence.