Hours to $100 net
5.7 hrs
Net target divided by the current city net hourly baseline.
Phoenix, AZ | Updated Sep 2026
Uber Phoenix $100 a Day $17.48/hr Net
Use this when the question is how many real hours and miles it takes to clear a $100 net day.
Net hourly
$17.48
Gross weekly
$703
Miles/week
256
Hours/week
25
Estimate transparency
How this Phoenix Uber $100 a Day estimate was built
This estimate uses 5 cited sources for local context. No city-specific driver report is included yet; 2 broader app benchmarks are shown separately.
What this estimate uses: The $100/day target is converted into required hours, miles, and gross pay from a $17.48/hr net baseline.
Cited sources
5
Driver reports
2
Local driver reports
0
Source review
Checked 2026-02-26
Direct answer
Uber Phoenix make $100 a day estimate
At the current Uber Phoenix side-hustle baseline of $17.48/hr net, a driver would need about 5.7 hours, roughly 59 miles, and about $161 gross to clear $100 net after mileage and tax assumptions.
This target gets harder when the app is slow, tips are weak, or a route forces unpaid return miles. Treat the $100/day number as a shift plan, not a guaranteed app promise.
Local operating context
What changes the $100 a day math in Phoenix
In Phoenix, demand is usable but uneven. During spring training and snowbird season, route governance and queue timing decide whether hours stay profitable.
In Phoenix side-hustle mode, prioritize Downtown, Tempe, and Old Town Scottsdale, cap transfer distance on I-10, Loop 202, and I-17, and route fallback through Biltmore and Chandler whenever spring training and snowbird season introduces conversion noise.
Conversion drop when leaving Downtown, Tempe, and Old Town Scottsdale
Route friction on I-10, Loop 202, and I-17
summer heat and AC-driven cost spikes
“My side-hustle rule is simple: protect a 18-dollar floor, keep the map tight near Downtown, Tempe, and Old Town Scottsdale, and switch once to Biltmore and Chandler before ending a weak block.”
“At 25-hour schedules, the winners are usually the people with weekly records and reserve discipline. Process quality matters more than optimism.”
Local sources checked
City of Phoenix: Phoenix Traffic Count Stations Service
Phoenix Sky Harbor International Airport: Phoenix Sky Harbor Airport Statistics
Phoenix Sky Harbor International Airport: PHX Passenger Record Press Release
U.S. Energy Information Administration: EIA Gasoline and Diesel Fuel Update
Internal Revenue Service: IRS Standard Mileage Rates
Goal math
Phoenix Uber target calculator
The useful answer is not only pay per hour. It is how many real hours and miles the target requires.
| Target | Modeled hours | Modeled miles | Gross needed | Best use |
|---|---|---|---|---|
| $100 net day | 5.7 hrs | 59 mi | $161 | Dinner, weekend, or two short peaks. |
| $200 net day | 11.4 hrs | 117 mi | $322 | Long stretch goal; compare against fatigue and dead miles. |
| Per-mile floor | 25 hrs/wk | 256 mi/wk | $2.75/mi | Reject offers that look busy but fail after route miles. |
Data-backed checks
$100 a Day metrics for Phoenix
Miles to $100 net
59 mi
Modeled mileage load at the hours needed for a $100 net day.
Gross needed
$161
Approximate app payout before mileage proxy and self-employment tax.
Evidence patterns
What the source data says to check
These cards turn driver discussions, official pay docs, field tests, and large driver datasets into the specific checks this page is trying to answer.
Target-income pattern
$100/day questions are really hours-and-miles questions
Driver discussions frame $100 as possible but market-dependent. For Uber Phoenix, this page translates the target into 5.7 modeled hours and 59 miles instead of treating the number as a guarantee.
Source: Uber $100/day discussion →Peak-window pattern
The target is easier in strong windows than all-day grinding
Driver-source comments repeatedly separate dinner, late-night, airport, event, and weekend windows from slow all-day availability. That is why this page links the target to hours and mileage.
Source: Uber nights/weekends discussion →Cost benchmark
$100 gross is not $100 net
At 59 modeled miles for a $100 net day, the IRS mileage proxy alone represents about $45 of vehicle-cost pressure before self-employment tax.
Source: IRS 2026 mileage rate →Driver field notes
What drivers check before trusting a Uber earnings number in Phoenix
These notes come from field tests, official platform docs, driver discussions, and gig-economy reports. They are not guarantees; they are the friction points a real driver would check before treating $17.48/hr net as realistic.
Field test
Miles can overwhelm a strong Uber fare day
A recent Uber field test reported about 10 active hours, 10 trips, and 305 miles. For Phoenix, the mileage load is why this page starts with $17.48/hr net instead of gross fare totals.
Source: NerdWallet Uber pay test →Online time
Drivers judge waiting time, not only booked trips
Uber's earnings tools show session summaries with online time, offers, and completed trips. That is the right mental model for comparing a city: unpaid waiting and repositioning time change the real hourly rate.
Source: Uber delivery earnings guide →Mileage floor
A low dollar-per-mile offer can erase the shift
Driver threads often use a dollar-per-mile floor before accepting work. The current 2026 IRS business mileage rate is $0.76/mi, so Phoenix drivers should compare every offer against total business miles, not only dollars.
Source: IRS 2026 mileage rate →Market timing
Peak windows beat all-day availability
Recent driver discussions keep repeating the same pattern: good markets can work at peak windows, while summer, school breaks, slow months, and driver saturation make all-day grinding much less reliable.
Source: Driver discussion on 2026 demand →Platform spread
Customer prices can rise while driver pay barely moves
Gridwise reported customer rideshare prices up 9.6% and platform fees up 33.2%, while driver gross pay per hour rose 4.1%. That gap is why net earnings pages need cost and time assumptions.
Source: Gridwise 2026 gig mobility report →Published shift evidence
Uber shift benchmarks used for Phoenix
Local reports are labeled separately from broader app benchmarks. These reviewed public examples do not prove a Phoenix wage; they only stress-test whether the modeled $17.48/hr estimate survives real mileage and time data.
Field test
rideshare driving
Broader benchmark
National Uber field test
10 active hours, 10 trips, and 305 miles
Gross
Not reported
Active hr
10.0
Dash/online
Not reported
Miles
305
Reported deliveries: 10
Uber screenshots need a mileage check because a strong fare day can still put heavy depreciation on the car.
Source: NerdWallet Uber pay test →
Reddit self-report
early-morning and surge-only driving
Broader benchmark
Tennessee UberX/Lyft year report
$23,611 gross after platform fees and tolls, 18,426 miles, $38 gross/hour, $1.28/mile
Gross
$23611
Active hr
Not reported
Dash/online
Not reported
Miles
18426
The driver used a 2014 Honda Civic and only drove selected surge and early-morning windows. The post does not provide enough verified time detail for a net-hourly estimate.
Source: Tennessee UberX/Lyft gross earnings report →Driver report intake
Share a real Uber shift in Phoenix
Modeled earnings are useful, but actual shifts are the data moat. Submit gross pay, miles, hours, and the window you drove so future Phoenix pages can compare the model against real driver reports.
Current model
$17.48/hr
Report status
Editorial review
Use the next page by intent
Related Phoenix Uber questions
After Gas
Use this when the gross payout looks fine but fuel and mileage may erase the shift.
Pay Per Mile
Use this when the real question is whether the offers clear a dollar-per-mile floor.
Active Time
Use this when app-reported active time may hide unpaid waiting and repositioning time.
Worth It
Use this when deciding whether the city is worth driving at a realistic side-hustle pace.
$1,000 a Month
Use this when planning a monthly side-income target instead of judging one shift.
Nights and Weekends
Use this when the plan is to drive around a 9-to-5 schedule instead of all-day availability.