C.E. Info Systems Ltd Mar 2026 : Order Book Surges 17% to ₹1,754 Crore Amid Delayed Government Cash Flow

Section 1 — At a Glance

C.E. Info Systems Ltd (MapmyIndia) concluded fiscal year 2026 with an aggressive sequential recovery in its final quarter, contrasting sharply with a softer operating run-rate observed across the preceding nine months. Total operational revenue for the full year experienced a highly measured expansion, moving from ₹463.25 crore in FY25 to ₹474.10 crore in FY26. This performance was primarily limited by deferred execution cycles and elongated procurement schedules within the public sector. Despite top-line friction, core operating discipline insulated the software-led ecosystem’s cost structure, enabling full-year absolute EBITDA to arrive at ₹175.50 crore with stable margins.

Investor attention is heavily concentrated on the substantial expansion of the company’s forward-looking metrics. The open order book scaled 17% to reach a record ₹1,754.40 crore, driven by robust deal wins in automotive telematics and enterprise application programming interfaces (APIs). However, structural working capital stress has emerged as an operational headwind. High-margin map data licenses are increasingly being bundled alongside capital-intensive IoT hardware deployments. This has severely impacted cash optimization, as inventory levels were intentionally built up to meet forecast demand. Additionally, trade receivables rose substantially from ₹133.00 crore to ₹176.41 crore, reflecting extended credit profiles common in large milestone-driven public sector contracts.

High operational growth visibility loses its value when internal liquidity remains tied up in multi-year balance-sheet commitments.

The immediate outlook depends on the company’s ability to efficiently convert this massive order backlog into high-margin SaaS revenue streams as structural reporting realignments take effect.

Section 2 — Introduction

C.E. Info Systems Limited (MapmyIndia) occupies a unique niche within India’s deep-tech infrastructure, serving as an indigenous, full-stack alternative to global mapping conglomerates. Incorporated in 1995, the company spent decades constructing highly detailed proprietary geospatial datasets before transitioning into a high-margin digital platform provider. This long-standing data advantage forms the backbone of its multi-product suite.

The current analysis is prompted by a notable inflection point in the company’s financial narrative. While headline annual numbers suggest a period of stabilization, the underlying operational mechanics tell a more dynamic story. MapmyIndia is currently navigating a dual shift: it is scaling its capital-intensive IoT-led tracking ecosystems while simultaneously re-routing its substantial government business into a specialized, wholly-owned subsidiary.

By analyzing the audited financial results for the period ending March 31, 2026, alongside corporate governance adjustments and recent order bookings, this report aims to unpack the structural realities behind the financial numbers.

Section 3 — Business Model: WTF Do They Even Do?

MapmyIndia functions as a digital data refinery, selling access to proprietary digital maps, geospatial software suites, and location-based IoT frameworks. The architecture operates across three distinct delivery layers: Maps-as-a-Service (MaaS), Software-as-a-Service (SaaS), and Platform-as-a-Service (PaaS). Instead of relying on volatile, one-time transactions, the business model primarily charges B2B and B2B2C enterprise clients via multi-year license fees, royalties, and subscription annuities.

The operational scale of the ecosystem is extensive, capturing approximately 99%+ of India’s road network through 6.5 million kilometers of digital roads. This database links together 7,900+ towns, over 6.37 lakh villages, 19 million distinct structural addresses, and more than 23 million points of interest. The business model is structured into two main product categories:

• Map-led Products: High-margin intellectual property licensing that feeds advanced 2D/3D navigation interfaces, high-definition ADAS telemetry, and location analytics into corporate enterprise systems and automotive dashboards.
• IoT-led Products: Hardware-enabled tracking bundles where cellular IoT sensors, video telematics, and fleet automation software are sold as operational packages.

While Map-led services generate strong software margins, the IoT-led vertical involves upfront asset deployment costs that influence corporate capital allocation.

Section 4 — Financials Overview

Figures are consolidated, in ₹ crore.

Comparison Table

Quarterly Trajectory Commentary

The sequential performance highlights a stark visual contrast: the final quarter single-handedly corrected a multi-quarter slowdown that occurred between June and December. Revenue surged 54.8% sequentially to ₹145.04 crore, lifting operating profitability right back up with it. EBITDA margins rebounded to 44.6% in Q4FY26, gaining support from a favorable revenue mix and an increasing proportion of SaaS-based subscriptions within the IoT division.

Quarterly earnings volatility is often the direct price paid for managing large enterprise and government contracts that rely on rigid billing milestones.

Did Management Walk the Talk?

Reviewing the latest updates reveals clear operational trends. Revenue for the full fiscal year arrived at ₹474.10 crore. While this absolute top-line growth appears modest relative to historic trends, management effectively met its core profitability targets, keeping consolidated EBITDA margins steady at 37%.

Management addressed previous analyst concerns by detailing the exact mechanics of the full-year revenue conversion bridge. Out of a starting order book of approximately ₹1,500 crore, the company converted roughly 17% to 18% into current-period revenue (approx. ₹270 crore). Concurrently, it secured ₹785.40 crore in entirely new order bookings throughout the year. Of these new contracts, ₹200 crore was billed immediately within the fiscal cycle, while the remaining ₹585.40 crore was added directly back into the forward pipeline.

The primary cause for the mid-year