BIZTRAC BETA
Rental and operating of own or leased real estate

TUNGA HOLDING AS

Org. no. 918148981 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −15.3m
Equity NOK 28.0m
Incorporated 2016
Share capital NOK 229,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TUNGA HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918148981. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 229,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet, fast eiendom og annen virksomhet beslektet med dette.”.

Key figures · 2024

Operating profit
NOK −15.3m
Equity
NOK 28.0m
Est. value
NOK 25.6m

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.4%
Good
Equity as a share of total capital

Who owns TUNGA HOLDING AS?

KAMC HOLDING AS
TUNGA HOLDING AS
· NOK −15.3m profit

TUNGA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TUNGA HOLDING AS own?

TUNGA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TUNGA HOLDING AS

Who owns TUNGA HOLDING AS?

KAMC HOLDING AS is the largest registered owner, with 100.0%.

Where is TUNGA HOLDING AS based?

TUNGA HOLDING 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.