12-hour weekend net
$112
Modeled net profit if weekend windows match the city baseline.
Dallas, TX | Updated Jul 2026
Use this when the plan is to drive around a 9-to-5 schedule instead of all-day availability.
Net hourly
$9.31
Gross weekly
$500
Miles/week
259
Hours/week
28
Evidence profile
Indexed because it has 5 cited local sources and a city-specific calculation model; driver reports are shown when available.
Unique data anchor: The schedule model focuses on dinner, weekend, and late-window demand instead of an all-day average.
Cited sources
5
Driver reports
3
City-specific
0
Method
city-rich-v4.0
Checked 2026-02-26
Direct answer
A nights-and-weekends plan for Uber in Dallas works best when the driver can compress demand into dinner, late-night, event, or airport windows. A 12-hour weekend at the current baseline models about $112 net, $214 gross, and 111 miles.
If those hours spill into slow gaps, the active-time screenshot can still look decent while the real all-in hourly rate falls.
Local operating context
Dallas rewards disciplined zone control around Uptown, Deep Ellum, and Legacy corridor; if you let sessions drift across I-635, US-75, and I-30, retained net drops quickly.
In Dallas side-hustle mode, prioritize Uptown, Deep Ellum, and Legacy corridor, cap transfer distance on I-635, US-75, and I-30, and route fallback through Bishop Arts and Addison whenever game days and fair-season weekends introduces conversion noise.
“My side-hustle rule is simple: protect a 23-dollar floor, keep the map tight near Uptown, Deep Ellum, and Legacy corridor, and switch once to Bishop Arts and Addison 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
Goal math
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 | 10.7 hrs | 99 mi | $192 | Dinner, weekend, or two short peaks. |
| $200 net day | 21.5 hrs | 199 mi | $384 | Long stretch goal; compare against fatigue and dead miles. |
| Per-mile floor | 28 hrs/wk | 259 mi/wk | $1.93/mi | Reject offers that look busy but fail after route miles. |
Data-backed checks
12-hour weekend net
$112
Modeled net profit if weekend windows match the city baseline.
Weekend miles
111 mi
Estimated mileage load for a 12-hour nights/weekends block.
Gross per weekend hour
$17.86/hr
Gross hourly baseline before expense and tax assumptions.
Evidence patterns
These cards turn driver discussions, official pay docs, field tests, and large driver datasets into the specific checks this page is trying to answer.
Schedule pattern
Driver discussions separate weekend/night performance from weekday availability. For Uber Dallas, this page models a 12-hour weekend and its 111-mile load.
Source: Uber nights/weekends discussion →Demand pattern
The useful check is whether dinner, late-night, airport, event, or bar-close demand offsets waiting and repositioning. Otherwise the shift can look good by active time and weak by all-in time.
Source: Uber earnings guide →Cost benchmark
A 111-mile weekend has about $80 of IRS mileage proxy cost before tax. The page keeps that number visible so weekend earnings do not become gross-only content.
Source: IRS 2026 mileage rate →Top-result comparison
The strongest search results usually win one trust signal at a time: official pay rules, a real driving test, a large driver dataset, fresh salary aggregates, or raw driver discussion. This page has to combine those signals with a city-level $9.31/hr net estimate.
Usually missing: Official pages explain how Uber pay works, but they do not answer whether nights and weekends in Dallas clears expenses.
GigVerdict response: Keep the official pay components visible, then convert the Dallas baseline into $9.31/hr net after mileage and self-employment tax.
Source: Uber official pay docs →Usually missing: Coverage pages confirm whether the platform is active, but they do not model a 259-mile week, local gas, or take-home pay.
GigVerdict response: Link users to the official availability check, then bring them back to the Dallas earnings model and calculator.
Source: Uber official city directory →Usually missing: One field test is vivid, but it is not a city-by-city planning system and may not match this market, schedule, or vehicle.
GigVerdict response: Use field-test friction as evidence, while keeping the Dallas page specific to $500 gross, 259 miles, and 28 hours.
Source: NerdWallet Uber field test →Usually missing: Large app-wide datasets are strong, but they usually flatten Dallas timing, traffic, and vehicle-cost differences.
GigVerdict response: Use large-data context as a sanity check, then expose local net hourly, per-mile, and target-hour calculations.
Source: Gridwise Uber pay data →Usually missing: Expert guides are useful, but broad app advice often stops before a city-specific after-expenses answer.
GigVerdict response: Translate the broad tactic into a Dallas planning page: hours, miles, gross needed, tax pressure, and related intent links.
Source: The Rideshare Guy Uber guide →Usually missing: Salary aggregators mix regions, worker types, and reporting methods, and rarely separate gross pay from 1099 costs.
GigVerdict response: Show a transparent 1099 model instead: $9.31/hr net after the 2026 mileage proxy and self-employment tax.
Source: Indeed Uber Driver salary data →Usually missing: Forum answers are fast and candid, but they are noisy, unstructured, and often hard to compare across cities.
GigVerdict response: Turn the driver pain points into structured checks for Dallas: active time, dead miles, target hours, and market timing.
Source: Uber driver discussion →Usually missing: Tactical posts help drivers operate, but they usually do not give a clean city URL for a single earnings question.
GigVerdict response: Make the page match one high-intent query, then point users into the calculator when their Dallas routine differs.
Source: ShiftTracker Uber driver guide →Usually missing: Policy pages explain why driver pay can feel broken, but they are usually not a shift-level earnings planner.
GigVerdict response: Keep policy and take-rate pressure as context while answering the practical net-pay question on the page.
Source: Seattle Driver Union pay calculator →Usually missing: Videos are persuasive, but they are slow to scan and rarely expose a reusable city calculator or source trail.
GigVerdict response: Answer the creator-style money question in text: whether Dallas can reach the target, how many hours it takes, and what miles it costs.
Source: Uber pay creator SERP →Driver field notes
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 $9.31/hr net as realistic.
Field test
A recent Uber field test reported about 10 active hours, 10 trips, and 305 miles. For Dallas, the mileage load is why this page starts with $9.31/hr net instead of gross fare totals.
Source: NerdWallet Uber pay test →Online time
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
Driver threads often use a dollar-per-mile floor before accepting work. The 2026 IRS business mileage rate is $0.725/mi, so Dallas drivers should compare every offer against miles, not only dollars.
Source: IRS 2026 mileage rate →Market timing
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
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
These are reviewed public field tests and driver discussions, not scraped personal data. When a source reports gross pay, hours, miles, or deliveries, GigVerdict shows those fields separately so the modeled $9.31/hr net estimate can be checked against real-world shift friction.
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 →$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 →$3,400-$4,000 monthly across six apps, with $3-$9 off-peak EV charging
Gross
Not reported
Active hr
Not reported
Dash/online
Not reported
Miles
Not reported
This is a multi-app delivery report, not Uber rideshare-only data. The useful evidence is that vehicle type, charging cost, peak-window selection, and app mix materially change the result.
Source: Uber Eats multi-app EV earnings discussion →Driver report intake
Modeled earnings are useful, but actual shifts are the data moat. Submit gross pay, miles, hours, and the window you drove so future Dallas pages can compare the model against real driver reports.
Current model
$9.31/hr
Report status
Editorial review