BIZTRAC BETA
Installation of insulation

ISOBYGG SOGN AS

Org. no. 911920603 Limited company (AS) Lærdal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 85,000
Equity NOK 1.2m
Incorporated 2013
Share capital NOK 100,000

ISOBYGG SOGN AS is registered as a limited company in Lærdal, Vestland with organisation number 911920603. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive entreprenørvirksomhet innen bygg og anlegg, salg og montering av isolasjonsprodukter og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 85,000
Equity
NOK 1.2m
Est. value
NOK 862,000

Financial health · 2025

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

Who owns ISOBYGG SOGN AS?

TERJE LOKREIM
ISOBYGG SOGN AS
NOK 2.3m rev. · NOK 85,000 profit

ISOBYGG SOGN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ISOBYGG SOGN AS own?

ISOBYGG SOGN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ISOBYGG SOGN AS

Who owns ISOBYGG SOGN AS?

TERJE LOKREIM is the largest registered owner, with 40.0%.

What is the revenue of ISOBYGG SOGN AS?

ISOBYGG SOGN AS had revenue of NOK 2.3m in 2025.

Who is the general manager of ISOBYGG SOGN AS?

Kjell Olav Cock is registered as general manager of ISOBYGG SOGN AS.

Where is ISOBYGG SOGN AS based?

ISOBYGG SOGN AS has its business address in Lærdal.

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.