BIZTRAC BETA
Rental and operating of own or leased real estate

TUNGA INVEST II AS

Org. no. 917367558 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 20.1m
Operating profit NOK 13.6m
Equity NOK 73.7m
Incorporated 2016
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TUNGA INVEST II AS is registered as a limited company in Oslo, Oslo with organisation number 917367558. 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 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andre eierandeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.1m in revenue and NOK 13.6m in operating profit.

Key figures · 2025

Revenue
NOK 20.1m
Operating profit
NOK 13.6m
Equity
NOK 73.7m
Est. value
NOK 68.2m

Financial health · 2025

Liquidity
3.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.5%
Good
Equity as a share of total capital

Who owns TUNGA INVEST II AS?

TRONDHEIM AREAL AS
TUNGA INVEST II AS
NOK 20.1m rev. · NOK 13.6m profit

TUNGA INVEST II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TUNGA INVEST II AS er morselskap for 9 datterselskaper:

Frequently asked questions about TUNGA INVEST II AS

Who owns TUNGA INVEST II AS?

TRONDHEIM AREAL AS is the largest registered owner, with 100.0%.

What is the revenue of TUNGA INVEST II AS?

TUNGA INVEST II AS had revenue of NOK 20.1m in 2025.

Where is TUNGA INVEST II AS based?

TUNGA INVEST II AS has its business address in Oslo.

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.