Gross per mile
$3.83/mi
Gross payout divided by modeled weekly miles.
Washington, DC | Updated Sep 2026
Uber Washington Pay Per Mile $29.51/hr Net
Use this when the real question is whether the offers clear a dollar-per-mile floor.
Net hourly
$29.51
Gross weekly
$1071
Miles/week
280
Hours/week
25
Estimate transparency
How this Washington Uber Pay Per Mile 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 offer floor is computed from $1071.00 weekly gross over 280 modeled miles, then checked against net hourly.
Cited sources
5
Driver reports
2
Local driver reports
0
Source review
Checked 2026-02-26
Direct answer
Uber Washington per mile estimate
The Uber Washington weekly model uses $1071 gross over 280 total modeled business miles, or about $3.83 gross per mile. After the mileage-cost proxy and tax reserve, the model is $29.51/hr estimated take-home.
Count pickup, repositioning, and unpaid return miles in your own total. Leaving those out makes a weak offer look stronger than it is.
Local operating context
What changes the pay per mile math in Washington
In Washington, demand is usable but uneven. During federal calendar shifts and security closures, route governance and queue timing decide whether hours stay profitable.
In Washington side-hustle mode, prioritize Navy Yard, Dupont Circle, and U Street, cap transfer distance on I-395, New York Avenue, and GW Parkway approaches, and route fallback through NoMa and Georgetown boundaries whenever federal calendar shifts and security closures introduces conversion noise.
Conversion drop when leaving Navy Yard, Dupont Circle, and U Street
Route friction on I-395, New York Avenue, and GW Parkway approaches
curb restrictions and sudden detours
“My side-hustle rule is simple: protect a 23-dollar floor, keep the map tight near Navy Yard, Dupont Circle, and U Street, and switch once to NoMa and Georgetown boundaries 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
District Department of Transportation: DDOT Traffic Safety Input Program
Metropolitan Washington Airports Authority: MWAA 2025 Passenger Record
District Department of Transportation: DDOT Home and Traffic Safety Dashboard Access
U.S. Energy Information Administration: EIA Gasoline and Diesel Fuel Update
Internal Revenue Service: IRS Standard Mileage Rates
Goal math
Washington 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 | 3.4 hrs | 38 mi | $145 | Dinner, weekend, or two short peaks. |
| $200 net day | 6.8 hrs | 76 mi | $290 | Long stretch goal; compare against fatigue and dead miles. |
| Per-mile floor | 25 hrs/wk | 280 mi/wk | $3.83/mi | Reject offers that look busy but fail after route miles. |
Data-backed checks
Pay Per Mile metrics for Washington
Net profit per mile
$2.63/mi
Net profit after mileage and tax assumptions divided by modeled weekly miles.
IRS mileage proxy
$0.76/mi
A benchmark for vehicle operating cost pressure in 2026.
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.
Acceptance floor
Drivers compare offers by mile before hourly math
Uber Washington is modeled at $3.83 gross/mi and $2.63 net/mi. That mirrors driver-source behavior: screen weak offers by dollars per mile before trusting an hourly total.
Source: Uber driver $/mile discussion →Cost benchmark
A good offer still has to clear vehicle-cost pressure
The same $0.76/mi IRS proxy used across the site gives this page a consistent comparison line. It is a tax benchmark, not a measurement of the vehicle's actual cash cost.
Source: IRS 2026 mileage rate →Winner pattern
Top pSEO pages make the query-specific comparison visible
Good pSEO examples expose the exact data point the searcher came for. Here, the page puts gross-per-mile, net-per-mile, and the mileage proxy next to the source trail.
Source: Gridwise Uber 2026 pay data →Driver field notes
What drivers check before trusting a Uber earnings number in Washington
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 $29.51/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 Washington, the mileage load is why this page starts with $29.51/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 Washington 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 Washington
Local reports are labeled separately from broader app benchmarks. These reviewed public examples do not prove a Washington wage; they only stress-test whether the modeled $29.51/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 Washington
Modeled earnings are useful, but actual shifts are the data moat. Submit gross pay, miles, hours, and the window you drove so future Washington pages can compare the model against real driver reports.
Current model
$29.51/hr
Report status
Editorial review
Use the next page by intent
Related Washington Uber questions
After Gas
Use this when the gross payout looks fine but fuel and mileage may erase the shift.
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.
$100 a Day
Use this when the question is how many real hours and miles it takes to clear a $100 net day.
$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.