Blocked Drains in Reigate
Reigate's separate sewer system creates two independent drainage pathways—foul water from toilets and sinks, surface water from roofs and patios—making blockages in Reigate property-specific and era-dependent. Victorian and Edwardian properties across RH2 and RH3 suffer from root intrusion and mineral accumulation; post-war homes in Reigate (RH4) often have misconnections. Modern Reigate properties (RH5) experience blockages from fat and wipe-induced clogs in plastic piping.
Blocked drains in Reigate stem from root intrusion in Victorian clay pipes, hard-water mineral deposits, and misconnections into the separate sewer system. Reigate's split foul and surface-water drains mean different blockage patterns by era; diagnosis requires understanding whether the foul or surface drain is obstructed across RH2–RH5.
Drainage in Reigate — what local engineers know
Reigate and Banstead Council regulates discharge into its separate sewer system; misconnections—washing machines, dishwashers, or gutters plumbed into the wrong drain—trigger enforcement notices. Thames Water's hard-water supply accelerates mineral crusting in Reigate's older bore pipes, narrowing the effective diameter. Root intrusion is endemic in Reigate's Victorian housing stock (20%), where clay pipes beneath garden patios fracture and tree roots colonise. The separate topology means a blocked surface-water drain in Reigate doesn't affect foul drainage, but combined blockages indicate system-wide silting or structural failure requiring CCTV investigation across Reigate's postcodes RH2–RH5.
- Hard water supply causes limescale accumulation in boilers, radiators and soil pipe joints — powerflush and descaling demand is high across Reigate
- Separate sewer system across most of Reigate: misconnections (e.g. washing machines plumbed into surface water drains) are a known local issue and can result in environmental enforcement action
- Ageing infrastructure in parts of Reigate means drain blockages from grease, wipes and root ingress remain the most common call-out reasons
- With 34% of properties built before 1920, salt-glazed clay drainage and lead-solder copper pipework are common — pipe collapse, root ingress and joint failure are recurring call-out drivers.
What happens when you call us in Reigate
- 1 Immediate dispatch. We find the nearest available engineer covering RH2/RH3 and confirm the ETA before the call ends.
- 2 On-site diagnosis — no guessing. The engineer inspects using professional-grade equipment including CCTV where needed and quotes a fixed price before work starts.
- 3 Job complete, report issued. You receive a written completion report. All work is guaranteed — same fault returns within the guarantee period, we come back free.
Who's responsible for drains in Reigate?
In Reigate, responsibility for a blocked or damaged drain depends on where the fault sits. As a homeowner you are responsible for the drains within your property boundary that serve only your home. Since the 2011 private sewer transfer, Thames Water is responsible for shared sewers and lateral drains beyond your boundary — even where they run under private land. Road gullies and highway drainage are maintained by Reigate and Banstead.
This matters because it determines who pays. If our engineer's CCTV inspection shows the fault is in a shared sewer, we'll tell you — and you can report it to Thames Water rather than paying for the repair yourself. The separate sewer layout that dominates Reigate affects where these boundaries typically fall, and our local engineers know the RH2, RH3, RH4 networks well enough to identify ownership quickly.
Blocked Drains prices in Reigate
Every Reigate job is quoted as a fixed price before work starts — what we quote is what you pay, with no call-out fee for providing the quote. The final price depends on access (an external inspection chamber is quicker than internal-only access), the pipe material and condition , and how established the blockage or fault is. Request your free quote and we'll confirm the price and your engineer's ETA in the callback.