Micromobility rentals usually lose rides and revenue in colder, wetter months. The useful question is not whether demand falls, but whether the remaining revenue justifies keeping every vehicle and service zone active.
Use local trip, fleet availability, revenue, and weather records to separate a normal seasonal decline from a short weather shock. Then choose full service, a smaller core fleet, temporary closures, or a seasonal pause.
Reported industry examples point in the same direction. They should guide your questions, not replace your own forecast.
What the available benchmarks show
Several published examples describe sharp winter declines, but they measure different things. Bird's US credit-card ride records fell 23% from October to November 2018, followed by another 27% decline in December, according to Robert Noland's analysis.
| Operator or source | Reported observation | Practical use |
|---|---|---|
| Bird, US, 2018 | Credit-card rides fell 23% from October to November, then another 27% in December | Illustrates how demand can weaken across consecutive months |
| Zoba market summary | Revenue declined more than 20% in 90% of markets, while 60% saw declines above 50% in February | Use as a stress-test range, not a universal forecast |
| TUMI finding | Cycling activity fell by about 50% during cold or winter conditions | Shows the possible effect of temperature on the wider cycling market |
| Bloomington example | Rides fell about 50% during cold or snowy conditions; rain reduced use by 20% to 50% | Helps frame local weather scenarios |
| Voi operator example | Winter ridership was reported at roughly half of warmer-period ridership | Shows how an operator-level result can differ from a market average |
The Zoba, TUMI, Bloomington, and Voi figures are summarized in the source material for this article and in GreenMoov's related seasonality analysis. The supplied material does not show one shared collection method, time period, or definition of revenue and ridership.
That distinction matters. Do not average these percentages together.
A ride count, cycling activity measure, and revenue figure are not interchangeable. Bird's monthly movement may reveal a pattern, while a Voi result may reflect one operator's fleet, pricing, and service area. Treat each as a directional benchmark.
Separate seasonality from weather and supply
Seasonality is the expected change in demand by month or season. Weather is the short-term effect of rain, snow, cold, or other conditions. Supply is everything the operator controlled that day.
Supply can mimic seasonality.
| Signal | What to compare | Why it matters |
|---|---|---|
| Calendar | Same weekday, month, and service period across comparable years | Reveals the normal seasonal baseline |
| Weather | Temperature, rain, snow, ice, and the duration of the event | Shows whether a particular day was unusually difficult |
| Fleet supply | Active vehicles, service hours, zones, and out-of-service units | Prevents a supply reduction from being mistaken for weak demand |
| Commercial activity | Prices, discounts, events, transit disruptions, or major closures | Explains demand changes that weather alone cannot |
A rainy Saturday with a full fleet is not comparable to a rainy Saturday when half the vehicles were unavailable. Neither is a February with reduced operating hours comparable to a normal February.
Start with your own data. That is the strongest available forecast.
Build a local seasonal demand baseline
A useful model does not need to be complicated. It needs consistent inputs and clear definitions.
-
Choose a comparison window. Use a full prior season if you have one. Mark unusual periods such as launches, major closures, severe storms, or extended vehicle shortages so they do not quietly shape the baseline.
-
Join weather to trip data. Add daily temperature, precipitation type, snow or ice conditions, and the length of each event. Use local conditions rather than a generic national temperature threshold.
-
Normalize for available supply. Track trips per available vehicle and revenue per vehicle-day, not only total rides. Record operating hours and the number of vehicles actually ready to rent.
-
Compare similar days. A weekday morning in one zone may behave differently from a weekend evening in another. Break the data down by service zone, vehicle type, and time period where the sample is large enough to be useful.
-
Create three operating cases. Build mild, expected, and severe scenarios. Apply the weather and seasonal changes you have actually observed, then use the Bird, Zoba, TUMI, Bloomington, and Voi figures as reasonableness checks.
-
Set a review trigger. Decide when you will revisit the forecast, such as after an unusually cold week or a sustained revenue shortfall. Write the review rule before the season begins.
Turns out, the hardest part is often not the calculation. It is keeping supply changes, weather events, and pricing changes in the same record.
Choose between full service, a smaller fleet, and a pause
The main decision should be based on contribution, not ride volume alone. Contribution is the revenue left after costs that vary with service, such as field labor, charging, recovery, and weather-related operations.
| Operating choice | When it may fit | Main tradeoff |
|---|---|---|
| Full network | Local demand remains strong enough to cover variable operating costs | Preserves coverage but may leave too many vehicles idle |
| Smaller core fleet | Demand remains concentrated in a few zones or periods | Reduces exposure while keeping a visible service |
| Temporary weather closure | Snow, ice, or severe conditions create a safety or service problem | Protects operations but interrupts trips and requires clear communication |
| Seasonal pause | Forecast contribution stays below avoidable cost for a sustained low-demand period | Cuts some operating expense but can weaken continuity and user retention |
A 50% ride decline does not automatically mean a 50% revenue decline. Average revenue per trip, discounts, vehicle mix, and customer behavior can change at the same time.
Fixed costs need their own line. Permits, insurance, software, storage, salaries, and contracted services may continue during a pause, depending on your agreements. Calculate which costs truly disappear before calling a shutdown profitable.
Check the city permit, concession agreement, and insurance terms before changing service. Requirements vary by location, and some agreements may address fleet caps, operating hours, parking, public communication, or temporary closures.
Thing is, a seasonal pause can save field costs while still creating a restart problem. Users may form new habits, vehicles may need inspection after storage, and the team may need time to redeploy the fleet.
Run a smaller winter operation
A reduced service can work when demand is weak overall but still reliable in a few places. Reduce by zone and time period rather than applying one blanket percentage to the entire fleet.
- Keep vehicles near corridors and destinations that retain demand.
- Match rebalancing and charging shifts to the shorter winter demand window.
- Use temporary weather actions before making permanent seasonal cuts.
- Tell riders about reduced hours, affected zones, and restart timing in the app.
Measure the result weekly. Watch rides per available vehicle, net revenue per vehicle, failed rental attempts, recovery time, and customer support contacts. If the smaller fleet produces similar utilization with lower operating cost, it may be better than keeping the full network active.
Do not hide a service reduction inside an availability problem. Record whether a vehicle was intentionally held back, awaiting repair, or unavailable because of weather.
Use weather as an operating trigger
Set the response before a storm arrives. A forecast should change preparation; observed conditions should change service; a recovery check should control the restart.
For rain, compare the local ride response with the cost of keeping the fleet deployed. A 20% to 50% drop may still support service in a dense area, especially if the decline is short and vehicles can remain available without extra field work.
Cold requires a different check. Look at both demand and vehicle performance, then reduce exposed inventory if the data shows that units will sit unused. Snow and ice may require a temporary closure or a zone-level restriction, but the exact rule should follow local safety procedures, permit terms, and the vehicle manufacturer's operating guidance.
Keep the trigger simple. Record the forecast, actual condition, action taken, and recovery time. After several events, you will know whether your threshold was too cautious, too loose, or aimed at the wrong metric.
Keep the winter fleet safe and ready
Winter demand does not remove maintenance work. Idle vehicles still need inspection, cleaning, tire checks, brake checks, light checks, lock checks, and documentation before they return to service.
Battery storage and charging guidance varies by model, chemistry, enclosure, and manufacturer. Follow the vehicle and battery manual for permitted temperatures, storage charge, removable-pack handling, and charging locations. Do not invent one charge percentage or temperature rule for every fleet.
Never charge a pack that is swollen, cracked, wet, unusually hot, or otherwise damaged. Remove it from service under your battery safety procedure and escalate it according to your approved handling process.
Store vehicles in a dry, secure area with a clear record of each unit's location and last inspection. To be honest, a simple storage log is often more useful than a complicated seasonal dashboard if it prevents missing units and rushed redeployment.
Forecast revenue rather than rides alone
A basic winter revenue model can start with:
Expected net revenue = forecast rides x average net revenue per ride
Use net revenue after discounts and refunds if those items are material in your market. Then subtract variable operating costs. Keep fixed commitments separate so a pause does not appear more profitable than it really is.
Run the formula under mild, expected, and severe demand cases. Test what happens if trips fall while revenue per trip stays flat, and then test a second case where pricing or trip mix changes. The purpose is not to predict one perfect number. It is to see which assumption could change the operating decision.
The Zoba figures give a useful stress case for February, while the Bird figures show how declines can build across fall and early winter. Neither tells you what your market will earn. Your own available-fleet and net-revenue history does.
FAQ
How much can micromobility rides fall in winter?
The reported examples range widely. Bird's US credit-card ride records fell 23% from October to November 2018 and another 27% in December. Voi was reported to see winter ridership at about half of warmer-period levels, while the Bloomington example showed about 50% fewer rides in cold or snow.
Those are benchmarks, not a standard industry rate.
Does a 50% drop mean the fleet should shut down?
No. Compare remaining net revenue with avoidable operating costs, then check whether demand is concentrated in a smaller group of zones. A reduced core fleet may preserve useful coverage without carrying the cost of a full network.
Are revenue declines and ride declines the same?
No. Revenue also depends on price, discounts, ride length, vehicle mix, and the number of paid trips. Model revenue separately from rides.
How should rain be compared with snow?
The reported examples associate rain with a 20% to 50% reduction in use and cold or snow with reductions near 50%. Your market may behave differently. Track the duration and severity of each event instead of treating every rainy or snowy day as equivalent.
What should operators track before making a seasonal decision?
Track rides, net revenue, available vehicles, operating hours, service zones, weather, maintenance downtime, charging work, field labor, and customer support contacts. These fields show whether demand fell, supply fell, or both changed together.
Can an operator pause service whenever winter demand drops?
Not necessarily. City permits, concession agreements, insurance terms, and local safety rules can affect operating hours and temporary closures. Review those documents before changing the public service.
Export your last comparable season's rides, available fleet, operating hours, net revenue, and daily weather. Build mild, expected, and severe cases from that file, then set the fleet and pause thresholds you will review after the next major weather event.