BIZTRAC BETA
Installation of insulation

ISOBYGG TROMS AS

Org. no. 923347887 Limited company (AS) Tromsø Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 21,000
Equity NOK 969,000
Incorporated 2019
Share capital NOK 100,000

ISOBYGG TROMS AS is registered as a limited company in Tromsø, Troms with organisation number 923347887. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Drive med isolering av nye og eksisterende bygg, og aktivitet som naturlig henger sammen med dette, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 21,000
Equity
NOK 969,000
Est. value
NOK 568,000

Financial health · 2025

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

Who owns ISOBYGG TROMS AS?

BRENDELØKKEN AS
ISOBYGG TROMS AS
NOK 2.4m rev. · NOK 21,000 profit

ISOBYGG TROMS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ISOBYGG TROMS AS own?

ISOBYGG TROMS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ISOBYGG TROMS AS

Who owns ISOBYGG TROMS AS?

BRENDELØKKEN AS is the largest registered owner, with 65.0%.

What is the revenue of ISOBYGG TROMS AS?

ISOBYGG TROMS AS had revenue of NOK 2.4m in 2025.

Who is the general manager of ISOBYGG TROMS AS?

Roy Arne Brendeløkken is registered as general manager of ISOBYGG TROMS AS.

Where is ISOBYGG TROMS AS based?

ISOBYGG TROMS AS has its business address in Kvaløya.

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.