BIZTRAC BETA
Installation of insulation

ISODREN MONTASJE AS

Org. no. 984698305 Limited company (AS) Frogn Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 70,000
Equity NOK 1.6m
Incorporated 2002
Employees 5
Share capital NOK 100,000

ISODREN MONTASJE AS is registered as a limited company in Frogn, Akershus with organisation number 984698305. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2002 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fuktsikring, drenering, tømrervirksomhet; nybygg, tilbygg og restaurering samt hva hermed står i forbindelse. Selskapet skal også kunne gi støtte til veldedige og allmennyttige formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 70,000
Equity
NOK 1.6m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns ISODREN MONTASJE AS?

JAN YNGVAR BALTZERSEN
ISODREN MONTASJE AS
NOK 3.2m rev. · NOK 70,000 profit

ISODREN MONTASJE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ISODREN MONTASJE AS

Who owns ISODREN MONTASJE AS?

JAN YNGVAR BALTZERSEN is the largest registered owner, with 51.0%.

What is the revenue of ISODREN MONTASJE AS?

ISODREN MONTASJE AS had revenue of NOK 3.2m in 2025.

Who is the general manager of ISODREN MONTASJE AS?

Jan Yngvar Baltzersen is registered as general manager of ISODREN MONTASJE AS.

Where is ISODREN MONTASJE AS based?

ISODREN MONTASJE AS has its business address in Drøbak.

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.