BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

MAHALINGAM AS

Org. no. 930075167 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 66.9m
Operating profit NOK 516,000
Equity NOK 1.5m
Incorporated 2022
Employees 17
Share capital NOK 500,000

MAHALINGAM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930075167. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2022 and has 17 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 66.9m in revenue and NOK 516,000 in operating profit.

Key figures · 2025

Revenue
NOK 66.9m
Operating profit
NOK 516,000
Equity
NOK 1.5m
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.9%
Good
Equity as a share of total capital

Who owns MAHALINGAM AS?

VETHA MAHALINGAM
MAHALINGAM AS
NOK 66.9m rev. · NOK 516,000 profit

MAHALINGAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAHALINGAM AS

Who owns MAHALINGAM AS?

VETHA MAHALINGAM is the largest registered owner, with 100.0%.

What is the revenue of MAHALINGAM AS?

MAHALINGAM AS had revenue of NOK 66.9m in 2025.

Who is the general manager of MAHALINGAM AS?

Vetha Mahalingam is registered as general manager of MAHALINGAM AS.

Where is MAHALINGAM AS based?

MAHALINGAM AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.