Two identical hydraulic systems can have wildly different lifespans, and the difference is often invisible: the amount of fine solid contamination floating in the oil. An ISO cleanliness code is the standardised way to state how dirty a fluid is, reducing a full particle count to three short numbers that reliability teams can compare, target, and trend. This guide explains what the three numbers in an ISO 4406 code mean, how each maps to a range of particle counts, and why holding a target cleanliness code is arguably the single biggest lever on the life of bearings, pumps, and valves.
ISO cleanliness code in one line: An ISO cleanliness code, defined by ISO 4406, is a three-number code that reports the concentration of solid particles in a hydraulic or lubricating oil sample at three size thresholds, conventionally 4, 6, and 14 microns. Each number is a range code standing for a band of particle counts per millilitre, so a code such as one written as three numbers separated by slashes summarises how contaminated the fluid is in a form that can be compared against a cleanliness target for the equipment.
An ISO 4406 cleanliness code is written as three numbers separated by slashes, and each number corresponds to a particle size threshold. The three thresholds are conventionally four microns, six microns, and fourteen microns, and the code counts all particles at or above each of those sizes. The first number reflects the many very small particles at or above four microns, the second the fewer particles at or above six microns, and the third the still fewer larger particles at or above fourteen microns. Reading left to right, the numbers move from the finest, most numerous debris to the coarser particles that do the most obvious damage.
Each of the three numbers is not a raw count but a range code. The standard divides the possible particle-count-per-millilitre values into bands, and each band is assigned an integer, so that one step up in the range number represents roughly a doubling of the particle count. This is why a small difference in the code represents a large difference in actual contamination: a code that is one number higher on a given size means about twice as many particles of that size and larger. That logarithmic scaling is what lets a wide range of contamination levels be captured in compact single-digit or two-digit numbers.
The reason three sizes are reported rather than one is that the shape of the contamination matters, not just the total. A fluid with many fine particles but few large ones behaves differently from one with a coarser distribution, and comparing the three numbers reveals the mix. The middle and coarse counts are especially telling because particles in those size ranges are close to the clearances in pumps and bearings, where they cause abrasive wear. Reporting all three keeps that information rather than collapsing it into a single, less useful figure.
The particle counts behind the code come from an oil analysis measurement, most commonly an automatic optical particle counter that draws a metered volume of fluid past a light source and sizes each particle by how much light it blocks or scatters. The instrument tallies particles at the standard size thresholds and the counts are converted into the three range codes. Because the method is sensitive, sampling technique matters a great deal: a sample taken from a live, turbulent line through a clean valve gives a representative result, while a sloppy sample from a still reservoir or a dirty port can report contamination that came from the sampling itself rather than the system.
A cleanliness code only becomes useful once it is compared to a target. Every hydraulic or lubricated system has a cleanliness level appropriate to its most sensitive component and its pressure, and equipment builders and reliability engineers set a target ISO code accordingly. A high-pressure servo system with tight clearances demands a much cleaner target than a low-pressure gearbox, because the same particle that passes harmlessly through a loose clearance can jam or erode a fine one. The measured code is judged against that target, and a result dirtier than target is a call to action, whether that means filtering the fluid, finding an ingress path, or investigating a failing seal.
Holding a target cleanliness code is widely regarded as one of the highest-value things a lubrication programme can do, because so much wear is driven by particles in the same size range as component clearances. Cleaner fluid means fewer abrasive interactions, slower fatigue, and longer life for bearings, pumps, and valves, so tightening a target and actually achieving it through better filtration and sealing pays back in extended component life. The code is the yardstick that makes this improvement measurable, letting a team prove that a filtration change genuinely moved the fluid to a cleaner band rather than just hoping it did.
A single cleanliness code is a snapshot, but the real value emerges from trending successive samples of the same machine. A code that holds steady near target says the filtration and sealing are keeping up, while a code that is drifting dirtier over successive samples says contamination is entering faster than it is being removed, or that a component is generating wear debris. Reading the direction of the code over time turns a routine oil sample into an early warning, often flagging a filter that has gone into bypass or an ingress point long before the contamination does visible damage.
Because cleanliness is a leading indicator, it pairs naturally with the other data a reliability programme collects. A rising particle count read alongside a rising wear-metal result and a change in vibration builds a much stronger case than any one measurement alone, so keeping the cleanliness code in the same asset history as those other parameters lets a reviewer see the whole picture. On systems fitted with inline particle sensors, cleanliness can even be monitored continuously rather than only at scheduled sampling intervals, catching a sudden ingress event as it happens.
This is where cloud SCADA and monitoring platforms fit into an oil-analysis programme. In distributed operations such as oil and gas production, hydraulically actuated equipment is spread across many remote sites, and a platform such as Merobix can hold each asset's cleanliness codes over time, compare them against the target for that machine, and raise the drift to a maintenance team the same way it raises a process alarm. Where inline particle counters exist, their live cleanliness output can flow into the same platform as any other tag, so a fleet operator sees fluid cleanliness trending across every site alongside pressures, temperatures, and flows rather than buried in separate lab reports.
Each number is a range code for the particle count at one size threshold, conventionally 4, 6, and 14 microns, counting all particles at or above that size. The numbers are ranges rather than raw counts, and each step up represents roughly a doubling of particle concentration. Reading left to right, they go from the many fine particles to the fewer large ones that clearances see most.
Much of the wear in bearings, pumps, and valves is driven by particles in the same size range as the internal clearances, which grind and fatigue surfaces as they pass through. Cleaner fluid means fewer of those abrasive interactions and slower fatigue, so holding a tighter cleanliness target directly extends component life. That is why controlling cleanliness is often called the single biggest lever a lubrication programme has.
The target is set by the most sensitive component in the system and the operating pressure, so a high-pressure servo system with tight clearances needs a much cleaner target than a low-pressure gearbox. Equipment builders and reliability engineers publish or specify these targets, and the measured code is judged against them. A result dirtier than target is a signal to filter the fluid, find an ingress path, or investigate a failing component.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.