sounds like a runs_per_hour vs capacity_per_run issue. there is likely a point where the decrease in runs_per_hour is offset by the increase in capacity_per_ru

sounds like a runs_per_hour vs capacity_per_run issue. there is likely a point where the decrease in runs_per_hour is offset by the increase in capacity_per_run. This assumes that the users will still use the service as long as the time_per_run (how long it takes to get from point A to point B) doesn't increase to a point where users choose to travel by different means.