P0133 reports a slow response from the upstream oxygen/lambda sensor, but exhaust leakage, fuel control, heater performance, contamination and engine conditions can slow the observed response.
Use the code as a measurement starting point, not a failed-part label. Preserve event data and compare symptoms, likely causes, live data and physical measurements under the same operating condition.
Generic/reference DTC context; manufacturer-specific meaning must be verified separately.
One DTC does not convict one part.
Freeze-frame and synchronized data put the symptom in context.
Controlled comparison narrows the root cause.
Clearing a code is not repair validation.
| Evidence | Observation / condition | Correct next action |
|---|---|---|
| Bank comparison | Both banks slow | Investigate shared fuel/MAF/temperature/heater causes. |
| Signal and trim | Sensor fast, trim slow | Inspect fuel control and injector response. |
| Leak effect | Worse at low flow | Check exhaust leakage upstream of the sensor. |
This file is not a parts-replacement list. Exact values should be used only after VIN, engine/transmission code, production period, software, test conditions and the manufacturer procedure are aligned.
Do not treat the code label as a parts diagnosis. Narrow root cause through freeze-frame, simultaneous module codes, power/ground, live data and active testing.
DTC Academy →P0133 · O2 Sensor Circuit Bank 1 Sensor 2 · Emissions control
Capture freeze-frame, first/last occurrence, load, rpm, temperature, vehicle speed and system voltage.
Rule out battery/charging, power, ground, fuses, network communication and shared-reference faults before replacing parts.
Compare commanded values with real sensor/actuator response under the same operating condition.
Clearing codes is not enough; recreate the monitor condition and verify that code/symptom does not return.
P0133 DTC meaning, symptoms, causes, freeze-frame, live data, circuit measurement, testing and misdiagnosis are consolidated in one technical record.
Preserve event data before clearing the code; verify vehicle identity and the relevant engine/transmission system before making a service decision.
The same DTC can lead to different root causes across manufacturers, controllers and operating conditions. Cross-check model, engine/transmission and the measurement chain.
Model Atlas → · Engine → · Transmission → · Workshop center →
Exact technical values, prices and failure rates are not invented without verified vehicle/manufacturer evidence.
This powertrain context reference is intentionally kept manufacturer-aware. Confirm the exact definition for the vehicle, model year and controller before replacing parts.
Save DTC status, freeze-frame/event data, operating state and companion codes before clearing memory.
Confirm the reporting module, supply, grounds, fuses and connector condition before judging a sensor or actuator.
Use live data to compare commanded state with actual feedback under the same operating condition.
Use the OEM procedure for pin locations and exact thresholds; separate electrical/network faults from mechanical, hydraulic, pneumatic or flow faults.
After repair, reproduce the original load and operating condition and confirm that the code and related symptoms do not return.
Browse model-specific measurement references → · Browse sourced model dossiers →
This code does not automatically condemn a component; it describes fault behaviour observed by the controller in a monitored system. Preserve event data and eliminate shared causes before narrowing the root cause with system-specific measurement.