.jpg)
Search "best hours to deliver" and you'll get the same answer everywhere: lunch rush, dinner rush, weekends, bar close. It's not wrong. It's just not actionable, because it ignores three things that actually determine your hourly rate:
- Market geometry. A dense urban core pays less per order but stacks several close-together drops an hour. A sprawling suburb pays more per order with fewer of them and long empty stretches between. "Dinner rush is best" means a completely different schedule in Chicago than in Phoenix.
- Driver supply, not just customer demand. 6:30pm Friday has the most orders and the most drivers online. The profitable window is usually the shoulder — the moment demand has spiked but supply hasn't caught up yet.
- Your own cost base. An hour with big gross earnings and 34 miles driven can net less than a quieter hour with 11 miles. Gross-per-hour is a vanity metric; net-per-hour after mileage is the number that matters. (See our IRS mileage rate 2026 guide for how the per-mile deduction factors into that math.)
The only reliable answer comes from your own data, measured consistently across every platform you run.
The 4 metrics that define a profitable hour
A "good area" is a zone where all four hold up at the same time. That's rarer than it sounds, and it moves by hour.
Peak hours: what the data actually says
Solo compared average hourly earnings across the four windows drivers plan their days around, in two very different market types. Each window is indexed against that market's overall average, so 100 = typical and 106 = 6% above typical.
Read that again: dinner peak is one of the worst-paying windows of the day, in both market types — 4% below average in dense cities, 6% below average in the suburbs. The pre-dinner shoulder is worse still. That's the opposite of what every "best hours" list tells you.
Why the busiest hours pay the least: busy isn't the same as profitable. Dinner rush has the most orders — that part of the conventional wisdom holds. But it also has the most drivers, because everyone's read the same advice. When supply outpaces demand: promotions dry up, you wait longer between offers (utilization drops even though the map looks red), and the good short-distance orders get taken instantly, leaving you the long hauls.
Lunch is the quiet winner in both markets — the strongest window in the data, with the fewest drivers competing for it. Late night lands at exactly average in both markets, which is more interesting than it looks: far fewer orders than dinner, but it pays the same as a typical hour because the competition has gone home. Fewer orders, but they're yours.
What this means for your schedule: the spread between the best and worst window is only about 10–13% — hour-of-day alone isn't where the big money is. Nobody transforms their income by moving from 6pm to noon. What moves the needle is stacking advantages: a good window, in a zone that pays, on a day when supply is thin, in weather that keeps other drivers home.
- If you can only work one block, make it lunch — best-paying window in both market types, least contested.
- Don't build your week around dinner. Fine if it's the time you have, but stop treating it as the default answer.
- Late night is underrated if it fits your life: average pay, minimal competition.
- Cut the pre-dinner shoulder first if you're trimming your schedule — it's the weakest window in the data.
The strategy differs by market, even though the hours look similar. Dense urban: low pay per order, more orders per hour, short drops — profit comes from density and stacking, so pick a compact zone and stay in it rather than chasing the biggest offer on screen. (Dense-urban drivers out-earn suburban ones at every window in the table, despite smaller individual orders.) Suburban sprawl: higher pay per order, fewer orders per hour, more miles — profit comes from route discipline, so anchor near a cluster of high-volume restaurants and decline anything that drags you outside it. Suburban lunch is the standout at 106, the highest index in the table.
The rule that applies everywhere: in dense markets you optimize for orders per hour; in sprawl you optimize for dollars per mile. Same app, opposite strategy.
Day-of-week: the pattern almost everyone gets wrong
Most drivers assume weekends win. Directionally true for volume — but hourly rate often holds up better midweek, because driver supply drops harder than demand does.
Across Solo drivers, the highest-earning day by hourly rate is [PH: day], and the lowest is [PH: day] — a gap of roughly [PH: XX]%.
Don't compare Saturday to Tuesday on gross earnings. Compare them on net hourly rate for the same number of engaged hours. Drivers who make that switch routinely find a quiet weekday block outperforms a crowded Saturday night, with fewer miles and less wear on the car.
Weather, events, and holidays: the swings worth planning around
If hour-of-day only moves your rate by ~10%, this is where the real variance lives.
Rain or snow. Bad weather is one of the most reliable earnings boosts on gig apps. When rain or snow hits, customer demand climbs while some drivers log off to avoid the roads — that supply squeeze is what pushes pay up. Drivers who stay out during a storm consistently report their best hours of the week. It's the same supply-and-demand logic that makes dinner rush disappointing, just running in your favor for once.
Major local events. Games, concerts, and festivals create a short, sharp window of high pay right as the event lets out. The lift isn't spread across a whole shift — it's concentrated in the 30–60 minutes after doors open or the final buzzer, and it's hyperlocal to the venue. Drivers who plan around the event calendar, rather than just driving around, catch pay noticeably higher than a normal shift.
Big food holidays (e.g., Super Bowl Sunday). These behave differently depending on what you drive. On delivery platforms like DoorDash and Instacart, food-holiday demand — wings, snacks, last-minute groceries — drives a real bump in both order volume and pay. For rideshare the effect is smaller and more mixed: people are staying in to watch, not going out. If you multi-app, these are the days to be on delivery rather than rides.
Two rules hold across all three: get online before the surge, not during it (by the time promo pay shows on screen, every other driver has seen it too — the margin is in the 20–30 minutes before), and events pay on the exit, not the entry (the profitable window around a stadium is post-event, in the residential ring around the venue, not the gridlock at its doors).
How Solo finds your profitable hours and areas automatically
Everything above is doable by hand — it's also a second job: exporting weekly summaries from three or four platforms, reconciling late-settling tips, logging mileage, and rebuilding a spreadsheet every week. By the time it's current, the week you'd have changed is already gone.
Solo does it continuously instead. Connect your gig accounts once, and Solo builds your market picture from your real completed work plus community earnings data in your city:
- Earnings heatmap. A map of your city colored by what drivers actually net there, not just where orders exist. Toggle by hour to watch the profitable center of your city move from the office core at noon to residential clusters at 8pm.
- Market intelligence by hour and platform. Ranks your hours the way the tables above do, but with your own numbers, per platform — so you know which app to sit on at 5:30pm and which to switch to at 9.
- Pay predictions and scheduling. Solo forecasts pay by hour and job using community earnings data across your market, so you can plan next week's blocks against expected rates instead of last week's memory — backed by Solo's daily Pay Guarantee. Ask Sherpa if you want the forecast explained in plain language before you commit to a block.
- Automatic mileage and true net. Solo's Mileage Tracker logs and auto-classifies mileage in the background, so every hour and zone is ranked on net, after the cost of getting there — the step manual spreadsheets almost always skip, and the one that changes decisions.
Where you sit as a driver:
- New driver (first 90 days): you don't have enough personal history yet. Lean on the heatmap's community layer to pick a starting zone, work it consistently for two weeks, then let your own data take over.
- Multi-app driver: the per-hour platform ranking is the whole game. Stop guessing which app to have open — schedule around the one that wins each block.
- Full-time pro: use day-of-week net comparisons to cut your two worst blocks and reinvest those hours into your best. Most drivers find the same money in fewer hours and fewer miles.
Your 7-day plan to find your best hours
- Connect every platform you drive for, so all earnings land on the same terms.
- Work one week normally — don't optimize yet, you need a clean baseline.
- Rank your hours by net $/hr, not gross. Note your top three and bottom three blocks.
- Open the heatmap by hour and identify the two zones that hold up in your top blocks.
- Cut your worst block next week and move those hours to lunch, or to a weekday when driver supply is thin.
- Log weather and events on outlier days, so you learn which conditions are worth going online for.
- Re-rank after week two. Two weeks of clean data beats two years of hunches.
FAQ
What are the best hours to drive for gig apps?
Lunch, from about 11:00am to 1:30pm, is the strongest window in Solo's data across both dense urban and suburban markets. It pays above average and draws the fewest competing drivers. Late night, from 9:30pm to 12:30am, lands at exactly average pay with far fewer orders, because most other drivers have gone home.
Is dinner rush actually the best time to drive gig apps?
No. Dinner peak, 6:00pm to 8:30pm, pays 4 to 6% below the daily average in Solo's data, and the pre-dinner shoulder from 4:30 to 6:00pm pays even less. Both windows have the most orders and the most drivers online at the same time, so the extra demand gets absorbed by extra supply instead of showing up in your hourly rate.
Does the best time to drive change between cities?
The windows themselves look similar in dense urban markets and suburban sprawl, but the strategy inside them doesn't. Dense cities pay less per order with more orders per hour, so drivers profit by stacking close-together drops in a compact zone. Suburbs pay more per order with fewer of them and more miles, so drivers profit by anchoring near a cluster of restaurants and controlling mileage.
Does weather affect gig driver pay?
Yes. Rain and snow are among the most reliable earnings boosts on gig apps. Demand climbs as riders and customers avoid walking or driving themselves, while some drivers log off to avoid the roads, and that supply squeeze pushes pay up. The advantage goes to drivers who get online before the storm hits, not after promo pay already shows on screen.
Do local events increase gig driver earnings?
Yes, in a short, hyperlocal window. Games, concerts, and festivals create a spike in pay concentrated in the 30 to 60 minutes after the event lets out, in the streets immediately around the venue. The gridlock at the doors before an event isn't the profitable moment — the exit is.
Is Super Bowl Sunday good for gig drivers?
It depends which app you're running. Food delivery platforms like DoorDash and Instacart see a real bump in both order volume and pay from wings, snacks, and last-minute groceries. Rideshare demand is smaller and more mixed on Super Bowl Sunday, since most riders are staying in rather than going out.
How much does hour-of-day actually matter compared to other factors?
Less than most drivers assume. The spread between the best and worst hourly window in Solo's data is only about 10 to 13%. Weather, events, and driver supply move your rate more than the clock does, which is why stacking a good window with a thin-supply day and bad weather matters more than chasing a single "best" hour.
How does Solo find my best hours and areas to drive?
Solo connects to every gig account you drive for and builds an earnings heatmap and market intelligence view from your real completed-offer data plus community earnings in your market. It ranks your hours by net dollars per hour, after mileage, and by platform, so you can see which app pays best in which hour instead of guessing.
