top of page

MTCTE Certification for IoT Devices, Step by Step: Scope, Tests and the Portal

Writer: Srihari Maddula
Srihari Maddula
18 minutes ago
18 min read
A black internet router with antennas and network cables on an office desk
Routers, Wi-Fi CPE and IoT gateways are among the products that need TEC MTCTE certification in India. Photo: Stephen Phillips (Hostreviews.co.uk) on Unsplash

The gateways are built, tested and boxed. The purchase order is signed. Then the buyer's procurement team sends one line back: please share the MTCTE certificate number for this model before we raise the invoice. Nobody on the engineering side has heard the acronym used about their own product. The radio module has a certificate, the power adapter has a BIS number, and the LoRa side went through type approval months ago. Surely that is enough?

It often is not. MTCTE, the Mandatory Testing and Certification of Telecommunication Equipment regime run by the Telecommunication Engineering Centre (TEC), is separate from radio type approval and separate from electrical safety registration. It applies to equipment that connects to a telecom network, and since Phase III and Phase IV took effect it reaches well into IoT: gateways, trackers, smart meters, smart cameras, smartwatches and more. A product that falls inside it needs its own certificate, tied to its own model number, before it can be sold, imported or used in India.

This guide walks through the regime the way a product team meets it: first the scope question, then the specific Essential Requirement, then the tests and the lab, then the portal, and finally what happens after the certificate is issued. Along the way it points out the design decisions that are cheap at schematic stage and expensive after the enclosure tooling is cut.

MTCTE certifies the product model, not the module inside it. A certified radio module is useful evidence. It is not the certificate the buyer is asking for.

Three Approvals That Get Confused

Most Indian IoT products meet three separate approval regimes, run by three different bodies, each asking a different question. Mixing them up is the most common reason a launch date slips.

WPC Equipment Type Approval (ETA) is about the radio. The Wireless Planning and Coordination wing asks whether a licence-exempt transmitter stays inside the band, power and emission limits set for it. A LoRa node on 865-867 MHz or a BLE sensor at 2.4 GHz needs ETA. We covered that process step by step in an earlier post.

BIS Compulsory Registration (CRS) is about electrical safety for specific product types notified by MeitY: power adapters, lithium cells and battery packs for portable equipment, and a list of IT and electronics products. For most IoT makers, CRS arrives through suppliers: the adapter maker holds the registration and supplies the number.

MTCTE is about the telecom side. TEC asks whether equipment that connects to a telecom network meets the Essential Requirements (ERs) for its product type: electromagnetic compatibility, safety, network interface behaviour, and increasingly security. The certificate is issued per model through the MTCTE portal.

Regime

Run by

Question it answers

Typical IoT trigger

Who usually obtains it

WPC ETA

DoT Wireless Planning and Coordination

Is the radio inside its exempt band limits?

LoRa, BLE, Wi-Fi, ZigBee transmitters

The product maker or importer

BIS CRS

Bureau of Indian Standards (MeitY scheme)

Is this notified product electrically safe?

Adapters, lithium cells and packs

Usually the component supplier

TEC MTCTE

Telecommunication Engineering Centre

Does this telecom product meet its ER?

Gateways, trackers, routers, smart meters

The product maker, or its Indian representative

The three overlap in places: an MTCTE ER often includes a safety parameter, for which TEC accepts a valid BIS certificate, and it lists radio parameters that echo what WPC checks. But one certificate never stands in for another, and none of the three certifies quality or reliability. Buyers increasingly ask for all three numbers on the same form.


Where MTCTE Sits in Law Now

MTCTE began under the Indian Telegraph rules, with Part XI added in 2017 to make testing and certification of telecom equipment mandatory. The legal ground has since moved. The Telecommunications Act, 2023 replaced the old telegraph law, and conformity assessment now sits under the Telecommunications (Framework to Notify Standards, Conformity Assessment and Certification) Rules, 2025, made under that Act.

For a product team the day-to-day mechanics have stayed recognisable. TEC still publishes the procedure, the ERs and the list of notified products. The working document is the amended MTCTE Procedure, version 3.0, published as TEC 93009:2024. It defines the schemes, the role of designated labs, the fee schedule (Annexure C), the product fee groups (Annexure A), and the rules on families and associated models.

Three practical consequences follow. First, read the current procedure, not a test house's summary from three years ago. The fee structure, scheme categories and validity rules have all changed since the early phases. Second, the notified product list and the mandatory dates come from TEC notifications, which have been amended many times; the latest notification wins. Third, the law treats certification as a condition of sale, import and use. A buyer's compliance team is not being fussy when it asks for the number. It is protecting itself.

When two documents disagree, the later TEC notification governs. Keep a dated copy of every notification you rely on in the product's compliance folder.

Is Your Product on the List?

MTCTE applies only to notified products, and each notified product has its own Essential Requirement document. The scope question therefore has a precise form: is there an ER whose product description matches what you are building?

The early phases covered classic telecom equipment: telephones, modems, PABX systems, transmission gear, routers and switches. Phase III and Phase IV, announced by TEC in September 2021, pulled in a large share of connected devices. The IoT-relevant entries include the IoT Gateway, Tracking Device (with standalone vehicle, human and pet variants), Smart Electricity Meter, Smart Camera, Smartwatch, Feedback Device, and End Point Device for Environmental Monitoring. Phase V added further items such as 5G base stations, hypervisors and IP terminals, mandatory from July 2024.

The mandatory dates were deferred several times while labs built capacity, the last of them (smart electricity meters, satellite communication equipment and three others) to October 2024. By late 2026 all of these dates are in the past, so for a product launching now the answer is simple: if an ER matches, certification is mandatory.

Product (ER)

Phase

Why IoT teams meet it

Scheme after 2024 re-categorisation

IoT Gateway

III

LoRaWAN, BLE or ZigBee gateways with Ethernet or cellular backhaul

SCS

Tracking Device

III

Vehicle, personal and pet trackers with GNSS and cellular

SCS

Smart Electricity Meter

III

Meters with a communication module

Check current list

Smart Camera

III

Connected cameras, including edge AI cameras

Check current list

End Point Device for Environmental Monitoring

III

Connected air, water or weather stations

Check current list

Wi-Fi equipment in 2.4 and 5 GHz bands

III

Access points, CPE, WLAN controllers, Wi-Fi routers

Check current list

The scheme column is where most teams go wrong, so we return to it below. For now the rule is to find the ER, download it from the portal, and read its scope clause before anything else.


The Sensor Node Question

The hardest scope call in IoT is the end node. A battery-powered LoRa soil sensor talks to a gateway over a licence-exempt radio. It does not connect directly to a public telecom network, it has no SIM, and it has no IP stack facing the internet. Does it need MTCTE?

The honest answer is that it depends on whether a notified ER describes it, and the default reading for a plain LoRa or BLE sensor is that the gateway is the telecom product while the node needs WPC ETA for its radio. The gateway ER itself makes this split visible: it lists LoRa, Sigfox, BLE and ZigBee as interfaces of the gateway, tested against the radio standards and the WPC rules, while the network-facing side (Ethernet, cellular, IP) is what makes it a telecom product.

Three cases break the default. The first is a node that is itself a notified product type. An environmental monitoring station that reports air or water quality may fall under the End Point Device for Environmental Monitoring ER even if it uses LoRa. Read that ER's scope clause before deciding it is out. The second is a node with a cellular modem. An NB-IoT or LTE-M water-level sensor connects directly to an operator network. If an ER matches it (a tracker, a meter, an environmental end point), the certified module inside does not certify the host. The third is a node that the buyer's tender lists as requiring MTCTE regardless. Tender language is not law, but it decides whether you get paid.

Write down the scope decision for every product, with the ER numbers you checked and why each did or did not match. When a buyer asks in two years, that note is the answer.

For genuinely unclear cases TEC runs a helpdesk (help.mtcte.tec@gov.in). A written answer to a specific product description is far stronger evidence than any consultant's opinion, including ours.


Running the Scope Check

We use a small script during product definition to turn the questions above into a checklist. It does not decide anything. It lists which regimes to investigate for each product variant, so the compliance budget is visible before the first prototype order, not after the first purchase order.

RADIO_865 = {"lora", "sigfox", "6lowpan-865"}
RADIO_24 = {"ble", "zigbee", "wifi-2g4", "6lowpan-2g4"}
CELLULAR = {"lte-m", "nb-iot", "lte", "5g", "gsm"}

def check(p):
    out, radios = [], set(p["radios"])
    if p["role"] == "gateway":
        out.append(("MTCTE", "IoT Gateway ER (SCS): test every interface fitted"))
    if p["role"] == "tracker":
        out.append(("MTCTE", "Tracking Device ER: GNSS incl. NavIC parameters"))
    if p["role"] == "env-endpoint":
        out.append(("MTCTE?", "Environmental Monitoring ER: read its scope clause"))
    if p["role"] == "router-cpe" or "wifi-5g" in radios:
        out.append(("MTCTE", "2.4/5 GHz ERs: security testing applies to CPE and routers"))
    if p["role"] == "node" and radios & CELLULAR:
        out.append(("MTCTE?", "cellular end device: module certificate may not cover host"))
    if radios & (RADIO_865 | RADIO_24 | {"wifi-5g"}):
        out.append(("WPC ETA", "licence-exempt radio: ETA for import and sale"))
    if p.get("mains_adapter"):
        out.append(("BIS CRS", "adapter: supplier's BIS registration number"))
    if p.get("li_battery"):
        out.append(("BIS CRS", "lithium cells/packs: IS 16046 registration from cell maker"))
    if not any(r[0].startswith("MTCTE") for r in out):
        out.append(("MTCTE", "no matching ER found: record the reasoning"))
    return out

print(check(dict(role="gateway", radios=["lora", "lte"], mains_adapter=True)))
print(check(dict(role="node", radios=["lora"], li_battery=True)))

Run against six typical product variants, it gives the split you would expect. A LoRaWAN gateway with Ethernet and LTE backhaul and a 12 V adapter returns three items: MTCTE under the IoT Gateway ER, WPC ETA for the LoRa radio, and the adapter's BIS number. A battery LoRa soil sensor returns WPC ETA and the cell maker's BIS registration, with a note to record why no ER matched. An NB-IoT water-level node returns an open MTCTE question and the battery registration. A LoRa air-quality station returns an open MTCTE question on the environmental monitoring ER, which is exactly the case most teams miss.

The value is less in the code than in the habit. Every variant gets the same questions, in the same order, and the answers go into the product's compliance folder with the date and the documents checked.


GCS and SCS: What Changes for You

MTCTE has two certification schemes. Under the General Certification Scheme (GCS), the applicant submits test reports from a designated lab, and TEC evaluates them parameter by parameter before issuing the certificate. Under the Simplified Certification Scheme (SCS), the applicant tests the product against the ER and submits a test-wise compliance sheet with a Self-Declaration of Conformity (SDoC); test houses describe the reports as held by the applicant rather than evaluated by TEC in the normal course. Every other rule of GCS applies to SCS.

In December 2023 TEC re-categorised the notified products, effective 1 January 2024. A short list of heavier network equipment stayed in GCS: cellular base stations, repeaters, compact cellular networks, E-band radio relay and similar. Many others moved to SCS. The published SCS list includes the IoT Gateway and the Tracking Device, along with classic customer equipment such as modems, fax machines and conferencing equipment.

The same notice changed the fees: for ER-based applications, only an administrative fee is charged, whichever scheme applies. That removed most of the cost difference between the schemes.

Two cautions follow. SCS is not a lighter test regime. The product must still be tested against every applicable parameter of the ER, and a self-declaration that turns out to be wrong is a far worse position than a rejected GCS application. Keep the full test reports, the lab's accreditation and the sample identification together, because any later audit or buyer query starts there. Second, the scheme for a given product is set by TEC's current categorisation, not by what you would prefer. The ER document itself states the scheme on its cover page: the 2024 IoT Gateway ER, for instance, reads Certification Scheme SCS and Product Fee Group B.

SCS shortens the paperwork, not the testing. Plan the lab work as though TEC will read every page of the report, because a buyer's auditor may.

Reading an Essential Requirement

The ER is the document that turns MTCTE from an acronym into a test plan. Each ER lists the product's variants, and for each variant a table of parameters with the standard each one is tested against. Some parameters apply to every product of that type; others are tied to interfaces, and those matter only when the interface is fitted.

Taking the 2024 IoT Gateway ER as an example, the parameter groups look like this:

Parameter group

What is tested

Standard named in the ER

Emissions

Conducted and radiated emission, Class A or Class B

CISPR 32 / EN 55032

Immunity

ESD, radiated RF, fast transients, surges, conducted RF, AC and DC dips

IEC 61000-4-2, -3, -4, -5, -6, -11, -29

Safety

IT equipment safety

IS 13252-1, IEC 60950-1 or IEC 62368-1

IP layer

IPv4, IPv6 and dual-stack behaviour

RFC 791, RFC 2460/8200, RFC 4213

Identity

Non-zero IMEI or MEID, or a unique MAC

ER annexure

LoRa and Sigfox

865-867 MHz short-range device limits

ETSI EN 300 220-2 V3.2.1 and WPC GSR 564(E)

BLE and ZigBee

2.4 GHz wideband transmission

ETSI EN 300 328 V2.2.2 and WPC GSR 45(E)

Wi-Fi

2.4 GHz and 5 GHz operation, EIRP per WPC rules

EN 300 328, EN 301 893 or FCC Part 15 equivalents

Cellular

LTE, NB-IoT, 5G NR conformance clauses

3GPP TS 36.521-1, TS 38.521 series

GNSS

GPS and NavIC for IoT

Annexure to the Tracking Device ER

Read the variant list first, then mark each parameter as applicable or not applicable with a reason. A LoRa gateway with Ethernet and LTE backhaul has no Wi-Fi, DSL or optical interface, so those rows are not applicable. Everything else applies. That marked-up ER becomes the lab's scope of work, and it is the single most useful document to have before requesting a quote.


Design Decisions the ER Forces Early

Several ER parameters reach back into the design, and they are much cheaper to meet at schematic and firmware-architecture stage than at the lab.

IPv6 and dual stack. The gateway ER lists IPv4, IPv6 and dual-stack parameters. A gateway whose network stack was built IPv4-only, because the first customer's network was IPv4-only, has a firmware problem, not a paperwork problem. Choose a stack that supports dual-stack operation from the start, and test it on the bench before booking the lab.

Unique identity. The ER expects a non-zero IMEI or MEID, or a unique MAC address. In production this means MAC addresses come from a registered block, are programmed per unit by the test fixture, and are logged against the serial number. Prototypes that all share one default MAC will fail this row and cause network faults in the field anyway.

Emission class. Class A (commercial and industrial) and Class B (residential) have different limits. A shed controller sold to farms and a gateway mounted in a home are not the same case. Decide the class with the sales team, because the enclosure, cable filtering and layout margin follow from it.

DC dips and surges. The immunity list includes DC voltage dips and short interruptions as well as surges. A gateway powered from a solar-battery system or a 12 V vehicle supply needs hold-up and brown-out behaviour that recovers cleanly. Firmware must restart into a known state, not into a half-configured radio.

GNSS with NavIC. Trackers and gateways with positioning are tested for GPS and NavIC parameters. A GNSS receiver without NavIC support turns into a component change late in the project.

The cheapest MTCTE fix is the one made in the requirements document. Mark the ER parameters that touch design in the product specification, next to the radio and power budgets.

Choosing a Designated Lab

MTCTE testing is done by Conformity Assessment Bodies (CABs) designated by TEC. The portal lists them with the parameters and product types each is designated for. A lab that is excellent for EMC may not be designated for the IP-layer or cellular parameters of your ER, so match the lab's designation scope to the marked-up ER, row by row.

Four rules shape the choice. First, the procedure generally does not allow a designated lab to sub-contract parameters it is not designated for to another lab and issue the result under its own name. If one lab cannot cover the whole ER, plan for reports from more than one lab and check that the portal accepts the combination for your product. Second, the notifications have set an age limit on test reports, commonly two years at the date of submission on the portal. A report from an early prototype run may expire before the application is filed. Third, for safety parameters, TEC accepts a valid BIS certificate, or a report from a BIS-recognised lab, for the safety standard named in the ER. If the product or its power section already holds BIS registration, reuse it rather than retest. Fourth, in the early phases TEC allowed reports from ILAC-accredited foreign labs for some products as a transitional relaxation. Those relaxations were product-wise and time-bound; do not plan around one without checking the current notification.

Ask each candidate lab for the parameter list it will test, the sample count it needs, the configuration it expects (test firmware, radio modes, cables, a way to force continuous transmission), and the lead time to report. A lab quote that does not name every ER parameter is not a quote, it is an estimate.


One Report, Many Models

Product lines rarely have one model. A gateway may come in an LTE version and an Ethernet-only version, in two enclosure colours, with two antenna options. The procedure gives three tools for this, and using them well saves both test fees and months.

Associated models. The procedure allows associated models to be included in a single test report, where the models share the design aspects that the tests examine and differ in ways that do not affect the results. A colour change or a label change is the obvious case. A different radio or a different power section is not.

Family certification. Where several models form a family under the procedure, they can be certified together. The portal FAQ states that the certification fee for all family certification falls in fee Group D. The rules on what counts as a family are in the procedure (clause 5.3 and Annexure B, as the FAQ points out), and they are worth reading before the product line is frozen.

Module reuse. TEC has allowed reuse of test reports for a common communication module across models in at least one product type: test reports for the communication module of smart electricity meters can be used for other meter models from the same maker using the same module. That pattern is useful precedent when designing a platform, but it is product-specific, so check whether an equivalent notice exists for your ER.

The certificate itself is model-specific. The portal FAQ is direct about it: if the model number changes, a new MTCTE certificate is required. This is one reason to keep marketing names separate from regulatory model numbers. A new colourway should not need a new model number; a new radio should.


Building the Evidence Pack

Before opening the portal, assemble everything in one folder. The portal asks for these items at different stages, and a missing document at stage four sends the application back to the queue.

product: LoRaWAN gateway, outdoor, LTE + Ethernet backhaul
model_no: GW-OUT-L1          # regulatory model number, as on the label
er: IoT Gateway ER, version as downloaded on 2026-11-02
variant: Variant 1 (IoT Gateway)
scheme: SCS                   # as stated on the ER cover page
applicability:                # one line per ER parameter
  emission_class_A: applicable
  ipv6: applicable
  dual_stack_rfc4213: applicable
  wifi_2g4: not applicable (no Wi-Fi fitted)
  lora_865: applicable
  lte: applicable
  gnss_navic: not applicable (no GNSS fitted)
test_reports:
  - lab: designated CAB A, emissions + immunity + IP layer, issued 2026-09-18
  - lab: designated CAB B, LTE + LoRa radio parameters, issued 2026-10-04
safety: BIS registration of the product, IS 13252-1
bom: full BOM with radio module part numbers and module certificates
documents: [block diagram, user manual, label artwork, photos inside and out]
signatory: authorised signatory letter on company letterhead

Three items catch teams out. The BOM: the portal's pre-check step reviews product details and the bill of materials, and the flow chart allows a limited number of BOM corrections (three, in the published flow chart) before the application must be restarted. Get it right first time. The model number: it must match the label artwork, the test reports and the user manual character for character. The applicability note: it is the reasoning behind every not-applicable row, and an evaluator who sees a gap will ask about it.


The Portal, Stage by Stage

Applications go through the MTCTE portal, www.mtcte.tec.gov.in. The published flow chart breaks the process into five stages.

Stage

What happens

What to have ready

1. New user registration

Create the applicant login

Company identity, authorised signatory, contact email

2. Applicant or OEM profile

Profile submitted and accepted by TEC

Company documents; for foreign OEMs, the Indian representative's details

3. Product details and BOM pre-check

Select the ER, enter product details, submit BOM to the pre-check evaluator

Final BOM, model number, ER variant; limited corrections allowed

4. Application and fees

Pay applicable fees online through NTRP, upload test reports or compliance sheet

Reports, SDoC for SCS, applicability notes, documents

5. Evaluation and certificate

Evaluator or validator raises queries through the portal's dialogue box; certificate issued

A named person to answer queries quickly

The profile step is often the first delay. It is done once per company, so do it early, before the product exists. A foreign maker works through an Authorised Indian Representative (AIR), an Indian entity that acts for it on the portal; an Indian integrator buying a foreign gateway should check that the maker's certificate for that exact model appears on the portal before importing it.

Stage five is where the calendar is won or lost. Queries arrive through the portal's dialogue box, and the clock waits for the applicant. A query asking why a parameter was marked not applicable, answered the same day with the applicability note, closes in a day. The same query answered after two weeks costs two weeks. Assign one person who owns the application and checks the dashboard daily.

When the certificate is issued it appears on the applicant's dashboard and on the portal's public Certified Equipment list. Buyers check that list. Make sure the model number and company name there match what the sales team quotes.

Register the company profile on the portal in the first month of the project, not the last. It costs nothing and removes the slowest dependency from the critical path.

A Planning Timeline

The calendar below is an illustration for a gateway with two radios, built from the stage structure above. It is not a promise; lab queues and query turnaround vary widely, and the real numbers come from your own lab quotes.

Week

Activity

Can run in parallel with

1-2

Scope check, download ER and annexures, mark applicability

Hardware design review

2-3

Portal registration and company profile

Lab quotes

4-8

Design for ER parameters (IPv6, MAC, emission class, DC dips)

Firmware feature work

8-10

Pre-compliance EMC and radio checks on prototype

Enclosure tooling

11-14

Formal tests at designated labs

Production test fixture build

14-15

BOM pre-check and application submission

Label artwork

15-18

Evaluation queries and certificate

First production batch

The structure matters more than the numbers. Registration, ER reading and design changes all happen before formal testing. Formal testing happens on production-intent hardware with frozen firmware for the tested parameters. The application is filed the week the last report arrives, not a month later.


After the Certificate: Labels, Changes and Renewal

A certificate brings obligations along with it. The product must carry the certification marking. TEC's guidance shows the label format with the certificate number, written as "MTCTE : XXXXXXXXX". Put it on the rating label, in the user manual and on the packaging where the procedure asks, and make sure the label artwork submitted is the one production uses.

Certificates issued from July 2022 onwards are valid for ten years. On renewal the original certificate number is kept, which keeps buyer records and tender documents valid across the renewal.

Changes are where post-certification discipline matters. The certificate covers the model as tested. A firmware update that changes radio behaviour, a new antenna, a different power section or a different cellular module can take the product outside what was tested. The procedure provides for certificate modification, and the rule that a model number change needs a new certificate means engineering change control and regulatory control must talk to each other. A simple test helps: if a change would alter any test result on the marked-up ER, it is a regulatory change and needs a decision before release.

Security is also moving into the ERs: for Wi-Fi customer premises equipment and IP routers, security testing became mandatory from 1 July 2024. Design as though it will reach your product type at the next model or renewal: no shared default passwords, signed firmware updates, secure boot and a documented vulnerability-handling process.


A Monday-Morning Sequence

For a team with a connected product heading to the Indian market, the order of work below avoids most of the delays described above.

  1. Run the scope check for every variant. List the ERs checked, the matches and the reasons. Ask the TEC helpdesk in writing about any product that sits on a boundary.

  2. Download the ER and its annexures. File them with version and date. Mark each parameter applicable or not applicable, with a reason.

  3. Register the company profile on the portal. For foreign OEMs, appoint the Authorised Indian Representative first.

  4. Put the design-affecting parameters in the specification. IPv6 and dual stack, unique MAC or IMEI, emission class, DC dips and surge, GNSS with NavIC where fitted.

  5. Fix the regulatory model number. One owner, one source of truth, used on the label, manual, reports and portal.

  6. Get lab quotes against the marked-up ER. Confirm designation scope for every parameter, sample count, configuration and lead time.

  7. Run pre-compliance on the prototype. Emissions, immunity and radio checks on the bench before formal testing.

  8. Test production-intent hardware. Time the formal tests so the reports are fresh at filing.

  9. File with a complete evidence pack. BOM, reports, safety evidence, applicability note, documents, signatory letter.

  10. Answer queries daily and plan for change control. After issue, route every hardware and firmware change through a regulatory check.


Back to the Certificate Number

The procurement team's one-line request is easy to answer when the work above has been done: a certificate number, a link to the portal's Certified Equipment list, and the WPC and BIS numbers alongside. It is hard to answer when the first time anyone reads the ER is after the gateways are boxed.


The difference is mostly timing. Scope at product definition, design for the ER during the schematic, test the production-intent build, and keep one owner for the paperwork. Done in that order, MTCTE is a predictable line in the plan rather than a surprise at the invoice.

EurthTech is an engineering-first product design and embedded systems company with a development center in Hyderabad. To discuss a project, write to connect@eurthtech.com or see https://www.eurthtech.com/case-studies.

Comments


EurthTech delivers AI-powered embedded systems, IoT product engineering, and smart infrastructure solutions to transform cities, enterprises, and industries with innovation and precision.

Factory:

Plot No: 41,
ALEAP Industrial Estate, Suramapalli,
Vijayawada,

India - 521212.

  • Linkedin
  • Twitter
  • Youtube
  • Facebook
  • Instagram

 

© 2025 by Eurth Techtronics Pvt Ltd.

 

Development Center:

4th Floor, Krishna towers, 100 Feet Rd, Madhapur, Hyderabad, Telangana 500081

Menu

|

Accesibility Statement

bottom of page