Order before 16:00 on business days? Shipped the same day!

Fast & reliable shipping throughout Europe

Expert customer service with professional advice

Mega Sale: Discounts up to 75%! While supplies last!

Error code P0133: meaning, causes, and solution

Foutcode P0133: betekenis, oorzaken en oplossing

Yasar Kocdas |

Your car still drives fine, but the check engine light is on and your fuel consumption is creeping up. You connect your scanner and see P0133. Don’t panic: this is almost never an acute problem. Often your lambda sensor has just aged and no longer responds as quickly as before. In most cases, you fix it with a new sensor.

Quick answer: Fault code P0133 means the lambda sensor (bank 1 sensor 1, the front sensor) responds too slowly. It switches too slowly between rich and lean, so the computer can’t adjust the mixture quickly enough. The most common cause is an old, slow sensor. You can keep driving, but your fuel consumption rises and your emissions worsen, so replace it in time.

What does fault code P0133 mean?

The lambda sensor before the catalytic converter measures how much oxygen is in your exhaust gas. Based on that, the computer continuously adjusts the mixture, a bit richer or a bit leaner. A healthy sensor switches quickly back and forth. If it responds too slowly, the computer sees that the response time is too slow and sets P0133. This concerns bank 1 sensor 1, the front sensor.

Severity: orange. It’s not an acute engine problem; you can keep driving. But the light stays on, you use more fuel unnecessarily, and your emissions worsen. If you let it go on too long, the catalytic converter underneath can suffer. So fix it in time.

Symptoms

Higher fuel consumption. Often the first thing you notice. The computer adjusts the mixture less accurately.

Check engine light on. Usually, the light stays on while the car continues to drive normally.

Slight decrease in smoothness. Sometimes the engine feels a bit less smooth or just a little less lively than you're used to.

Possible causes (from cheap to expensive)

Connector or wiring of the sensor (€10 to €80). A loose plug, corrosion, or a damaged wire slows down the signal.

Exhaust leak near the sensor (€20 to €100). If false air leaks in near the sensor, it measures incorrectly and responds slowly.

Sensor contamination (varied). Oil or coolant in the exhaust gas contaminates the measuring point, causing the sensor to slow down.

Worn, slow lambda sensor (€40 to €120). By far the number 1. Over time, the sensor becomes slow and no longer meets the response time.

Step-by-step plan: how to find the cause yourself

  1. Read the code. Connect a scanner and note if there are any other lambda codes (P0131, P0135).
  2. View the response time live. Read the response time or switching frequency of bank 1 sensor 1 in the live data. A healthy sensor switches back and forth quickly.
  3. Watch out for a slow sensor. If the value sticks or switches slowly, it indicates a sensor that no longer meets the response time.
  4. Compare with the sensor behind the catalytic converter. Place the front sensor next to the sensor behind the catalytic converter; the difference in switching behavior is often immediately clear.
  5. Check for exhaust leaks. Look and listen around the sensor for a leak that lets in false air, and check if the connector is properly attached.
  6. Replace the slow sensor and clear the code. If it all comes down to a slow sensor, replace it and clear P0133. If the code doesn’t return, the sensor was the problem.

How much does it cost?

Yourself: repair connector or wiring. €10 to €80. The cheapest solution if the sensor itself is still good.

Yourself: install a new lambda sensor. €40 to €120 for the part. Doable with a wrench or special socket.

Garage: diagnosis and replacement. €80 to €250, depending on the sensor and accessibility.

Fix it yourself or go to the garage?

Checking the connector, watching for exhaust leaks, and replacing a lambda sensor can be done quite well yourself with some tools. You mainly need a scanner that shows the live response time, so you can be sure the sensor is the culprit. If the sensor is stuck or you can't find the leak, a visit to the garage is wiser. The great thing about P0133 is that you first check cheaply and only buy a new sensor if the data confirms it.

The right tool for this code

For P0133 you mainly want to be able to do one thing: read the live response time of bank 1 sensor 1 and see how fast the sensor switches. These three tools fit that need. Start cheap with reading and clearing; for live sensor comparison, use a tool with good live data.

Related fault codes

P0133 belongs to a family of lambda codes. If you encounter one of these, the approach is similar: P0131 (sensor voltage too low), P0135 (sensor heater problem), and P0420 (catalyst efficiency below threshold, often due to a slow sensor). If you don’t yet know how to read and clear codes, first read reading and clearing fault codes.

Frequently Asked Questions

Can I keep driving with P0133?

Yes. It’s not an acute engine problem. However, you do consume a bit more fuel, your emissions worsen, and the light stays on. Fix it in time to protect the catalytic converter.

Is it always the lambda sensor itself?

Usually yes, but not always. First check the connector, wiring, and for an exhaust leak near the sensor. Only if those are fine is the sensor itself the likely cause.

How do I know if the sensor is really too slow?

Read the live data and check the response time or switching frequency of bank 1 sensor 1. A healthy sensor switches quickly back and forth; a slow sensor lingers.

Will I fail the MOT with P0133?

A lit engine warning light is a fail point. So fix the code before going for inspection.

In short

• P0133 = the lambda sensor (bank 1 sensor 1) responds too slowly.
• The most common cause is an outdated, slow sensor.
• Read the live response time and compare it with the sensor behind the catalytic converter.
• You can keep driving, but your fuel consumption will increase and you won’t pass the MOT with the warning light on.

View the diagnostic tools →