BIZTRAC BETA
Buying and selling of own real estate

IMMUTO AS

Org. no. 817205232 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 770,000
Operating profit NOK 565,000
Equity NOK 7.2m
Incorporated 2016
Share capital NOK 30,000

IMMUTO AS is registered as a limited company in Oslo, Oslo with organisation number 817205232. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i og eie aksjer i andre selskap. Kjøp, salg, rehabilitering, drift og utleie av eiendommer, virksomheter samt grossisthandel og agentur. Salg av konsulenttjenester og kompetanse som følger med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 770,000 in revenue and NOK 565,000 in operating profit.

Key figures · 2025

Revenue
NOK 770,000
Operating profit
NOK 565,000
Equity
NOK 7.2m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns IMMUTO AS?

JAN SKISTAD LINDBERG
IMMUTO AS
NOK 770,000 rev. · NOK 565,000 profit

IMMUTO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IMMUTO AS own?

IMMUTO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IMMUTO AS

Who owns IMMUTO AS?

JAN SKISTAD LINDBERG is the largest registered owner, with 100.0%.

What is the revenue of IMMUTO AS?

IMMUTO AS had revenue of NOK 770,000 in 2025.

Who is the general manager of IMMUTO AS?

Jan Skistad Lindberg is registered as general manager of IMMUTO AS.

Where is IMMUTO AS based?

IMMUTO 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.