Abstract

Free-floating car-sharing (FFCS) allows users to book a vehicle through their phone, use it and return it anywhere within a designated area in the city. FFCS has the potential to contribute to a transition to low-carbon mobility if the vehicles are electric, and if the usage does not displace active travel or public transport use. The aim of this paper is to study what travel time and usage patterns of the vehicles among the early adopters of the service reveal about these two issues.We base our analysis on a dataset containing rentals from 2014 to 2017, for 12 cities in Europe and the United States. For seven of these cities, we have collected travel times for equivalent trips with walking, biking, public transport and private car.FFCS services are mainly used for shorter trips with a median rental time of 27 min and actual driving time closer to 15 min. When comparing FFCS with other transport modes, we find that rental times are generally shorter than the equivalent walking time but longer than cycling. For public transport, the picture is mixed: for some trips there is no major time gain from taking FFCS, for others it could be up to 30 min.For electric FFCS vehicles rental time is shorter and the number of rentals per car and day are slightly fewer compared to conventional vehicles. Still, evidence from cities with an only electric fleet show that these services can be electrified and reach high levels of utilization.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.