E2E Networks Ltd. Company History and Annual Growth Details

The company was originally incorporated and registered as Private Limited Company on 20th August, 2009 vide Certificate of Incorporation issued by Registrar of Companies, NCT of Delhi and Haryana bearing Corporate Identification Number U72900HR2009PTC039406. Subsequently, the company was converted into Public Company pursuant to Shareholders resolution passed at the Extra Ordinary General Meeting held on 16.02.2018 and name of company was changed to ÂE2E Networks LimitedÂ pursuant to issuance of Fresh Certification of Incorporation dated March 14, 2018 by Registrar of Companies, NCT of Delhi and Haryana. The Corporate Identification Number of the company U72900HR2009PLC039406. The registered office of the company is situated at 282, Sector 19, Faridabad, Haryana-121002, India.

The company is in the business of providing Cloud Infrastructure in India. Since our inception in 2009, E2E has strived to attain technical innovation in the Cloud migration and Deployment for our clients. We were one the first companies to launch contract-less computing in India, way back in 2009. We followed this up by launching our hourly billed pure SSD (Solid-State-Drive) public cloud and private cloud. Our Cloud Infrastructure has been used by many well-known companies across industries like E-Commerce, Digital Classified, BFSI and whole host of new-age digital businesses

KEY EVENTS AND MILESTONES:

2009

- Incorporation of the company and commencement of business

2013

- Investment by a SEBI Registered Venture Capital Fund i.e. IL & FS Trust Company Limited-Trustee (Blume Ventures Fund I)

2014

- Investment by a SEBI Registered Alternative Investment Fund i.e. IL & FS Trust Company Limited-Trustee (Blume Ventures Fund IA)

2018

- Conversion of Company to Public Limited

Disclaimer: This is 3rd Party content/feed, viewers are requested to use their discretion and conduct proper diligence before investing, GoodReturns does not take any liability on the genuineness and correctness of the information in this article