Sector · GPR Survey
GPR Survey & Trenchless Works for Telecom Operators
Survey, permission and bore delivered on one programme by one company — because on a fibre rollout the thing that slips is never the drilling.
1.5 lakh kilometres and counting, a sustained ceiling of 100 km a day, and a record month of 700 KM in 30 days — every metre on our own equipment. Because mobilisation runs from Faridabad, sites beyond Delhi NCR carry a ₹1,00,000 per-project minimum. Inside NCR no minimum applies.
Quick AnswerMezux Touch works as a survey and trenchless delivery partner to national telecom operators and their EPC contractors. We are a registered service partner to leading national operators, and our delivered record includes 135 KM at Bawana, 225 KM for NDMC and 67 KM at Okhla, each completed under multi-authority compliance.
What an operator actually buys from a survey partner
Not metres. An operator buys the ability to hand a circle team a drawing they can build from without a stoppage, and to hand a programme office a format they do not have to normalise at quarter end.
Those two requirements pull in different directions, which is why survey packs are so often rejected: what suits a site engineer is a chainage schedule, and what suits design assurance is attributed data. A pack has to satisfy both rather than choosing one.
We build against the operator's own checklist rather than against a general survey specification, because a technically sound pack in the wrong format costs the same as a wrong one once the gang has demobilised.
Speed we can actually evidence
Our fastest recorded GPR delivery is 700 kilometres surveyed inside 30 days — sustained at over 23 kilometres a day on our own fleet, without renting a single system. A separate delivery covered 250 kilometres in the same 30-day window.
That pace is only possible because all 14 GPR systems and all 18 HDD rigs are company-owned. A contractor who rents cannot commit to a mobilisation date, because the date belongs to the rental yard rather than to them.
Where an operator has a fixed go-live and a compressed window, this is the difference between hitting a season and explaining why it was missed.
What the survey has to deliver for a fibre route
A telecom route needs more than a list of what is buried. It needs the crossings identified by chainage so a drilling supervisor can work from a schedule, depths annotated so the bore profile clears existing plant, and a drawing in the format the operator's own GIS will ingest without rework.
We issue layered CAD in the operator's convention, GIS files in SHP or KML, a PDF issue set for circulation and a signed report stating coverage and limitations. Where a route feeds a data centre or an enterprise campus, diverse-path verification proves the second route is genuinely separate rather than separate on paper.
Permissions handled on the same programme
Our liaisoning desk files and follows up road-cutting permissions with municipal bodies, PWD, NHAI, railways and metro authorities, and closes out restoration certificates afterwards. It is our own staff, not sub-let.
That matters on a rollout because an unclosed restoration certificate from an earlier stretch can hold the next application from the same applicant. We check that before filing rather than discovering it when a file stalls.
Working across an operator's national footprint
Crews mobilise across 28+ States/UTs, with dedicated GPR pages for 60 cities covering local ground conditions and the authorities that govern them. A national rollout does not need a different contractor in every circle.
Explore GPR survey by city, the HDD drilling and OFC works pages, or our delivered project record.
What an operator's QA team looks for
Operator quality teams reject survey packs for predictable reasons: depths quoted without a stated basis, no declared limitations, layer naming that does not match the operator standard, and crossings listed in a drawing rather than a schedule a site engineer can work from.
We build against that checklist rather than discovering it at submission. Detection method and confidence are carried as attributes on every feature, limitations are stated explicitly including areas of no access, and the crossing schedule is issued as a first-class deliverable.
Draft issue goes back for comment before the signed version, which is considerably cheaper than a rejected pack after the gang has demobilised.
Where survey saves a rollout the most money
Not in the metre rate. The savings sit in avoided redesign when a route is drawn around an obstruction that was known before design freeze, in avoided standby when a crew is not waiting on a clearance, and in avoided strike cost.
A single strike on a live service brings emergency response, asset-owner recovery charges, a stop-work notice and programme delay. Operators who have paid for one rarely argue about survey scope on the next circle.
Our delivered corridors were completed under multi-authority compliance and, in the NDMC and Okhla cases, materially below approved capex — which is the same argument expressed as a number.
What our crews have delivered, and on whose equipment
FAQ
Telecom Operators — common questions
Yes, and it is how most of our telecom work runs. Survey, RoW file and bore are scheduled against one another by one company, so the crew mobilises the week the sanction lands rather than the week after.
Our fastest recorded delivery is 700 kilometres in 30 days, sustained above 23 km a day on our own fleet. A separate delivery covered 250 kilometres in a 30-day window. Achievable pace depends on congestion and access on your specific route.
No. All 14 GPR systems and 18 HDD rigs are company-owned and crewed in-house, which is what lets us commit to a mobilisation date rather than checking a rental yard's availability.
Yes. We issue layered CAD in your convention plus SHP or KML, agreed in writing before drafting rather than corrected afterwards. Depth and confidence are carried as attributes on every feature.
Yes, through our own liaison desk covering municipal bodies, PWD, NHAI, railways and metro authorities, including restoration certificate closure and deposit release.
Outside Delhi NCR, minimum accepted GPR order value is Rs 1,00,000 per project, because crews and rigs mobilise from Faridabad. On circle-level rollouts this is rarely a constraint, since a single corridor normally exceeds it. No minimum applies within Delhi NCR.
We are a registered service partner to leading national operators. Delivered corridors include 135 KM at Bawana, 225 KM for NDMC and 67 KM at Okhla, each under multi-authority compliance.
Our ceiling on open corridors is around 100 km a day, achieved by running shifts through the night on our own fleet. A single 30-day programme has delivered 700 KM, which remains our record. In total we have completed more than 1.5 lakh km of GPR survey. The rate on your corridor will follow its congestion, the access you have and the confidence level you need.
Have a circle rollout with a fixed go-live?
Send the route schedule and target dates — we will work backwards from permissions and tell you what is deliverable.
Request a Sector QuoteGPR for telecom rollouts — specifications, standards and detailed questions
Mezux Touch works to operator quality standards rather than to a general survey specification, and the difference shows in what gets rejected. Operator QA teams return survey packs for predictable reasons: depths quoted without a stated basis, no declared limitations, layer naming that does not match the operator standard, and crossings buried in a drawing rather than listed in a schedule a site engineer can work from. We build against that checklist rather than discovering it at submission, because a rejected pack after the gang has demobilised costs far more than the survey did.
How the work is run
Survey is programmed against the rollout rather than against a survey calendar, so the corridor is cleared ahead of the construction front rather than months in advance when the data will have aged. Detection method and confidence are carried as attributes on every feature, because that is what an operator's design assurance process checks. Crossings are identified by chainage as the primary output. Draft issue goes back for comment before the signed version, so layer naming and format are agreed rather than corrected. Peak capacity is 100 km a day on open corridors, with a recorded best month of 700 KM in 30 days.
What you receive
A chainage-referenced crossing schedule as the primary deliverable, listing what crosses, at what depth, at what angle and with what confidence. Layered CAD in the operator's own convention plus SHP or KML for GIS ingestion without rework. A PDF issue set for circulation. A signed report stating coverage, limitations and areas of no access. Where diverse routing is in scope, a separate verification statement establishing whether two carrier paths remain genuinely physically separate. Consolidated reporting across circles so a national programme office reads one format rather than reconciling twelve contractors at quarter end.
Beyond the basics
What do operator QA teams reject most often? Depths without a stated basis, missing limitations, non-standard layer naming, and crossings presented as a drawing rather than a chainage schedule.
How fast can a circle corridor be cleared? Peak sustained output is 100 km a day on open corridors, with 700 KM in 30 days as our recorded best month. Your route depends on congestion and access.
Can you survey and drill under one contract? Yes, and it is how most of our telecom work runs. Survey, RoW file and bore are scheduled against one another rather than sequentially.
Will the drawing load into our GIS? Yes, in SHP or KML to your schema, agreed in writing before drafting rather than corrected after ingestion fails.
Can you verify diverse routing? Yes, as a separate statement. Two paths that look separate on a drawing occasionally share a duct nobody checked.
Terms used on this page
Crossing schedule — a chainage-referenced list of what crosses a route, which is the format a site engineer actually works from. Design assurance — an operator's internal review process, which checks how information was obtained rather than only what it says. Diverse path — two carrier routes intended to remain physically separate so one strike cannot take both. Circle — an operator's regional licence area, each typically run as its own programme. Draft issue — a preliminary drawing released for comment so format is agreed before the signed version.
