BIZTRAC BETA
Installation of insulation

ISOENERGI AGDER AS

Org. no. 921230109 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK −414,000
Equity NOK 104,000
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−414k kr).

ISOENERGI AGDER AS is registered as a limited company in Arendal, Agder with organisation number 921230109. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 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 3.9m in revenue and NOK −414,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK −414,000
Equity
NOK 104,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.8%
Satisfactory
Equity as a share of total capital

Who owns ISOENERGI AGDER AS?

ØYVIND PEDERSEN
ISOENERGI AGDER AS
NOK 3.9m rev. · NOK −414,000 profit

ISOENERGI AGDER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ISOENERGI AGDER AS

Who owns ISOENERGI AGDER AS?

ØYVIND PEDERSEN is the largest registered owner, with 65.0%.

What is the revenue of ISOENERGI AGDER AS?

ISOENERGI AGDER AS had revenue of NOK 3.9m in 2025.

Who is the general manager of ISOENERGI AGDER AS?

Øyvind Pedersen is registered as general manager of ISOENERGI AGDER AS.

Where is ISOENERGI AGDER AS based?

ISOENERGI AGDER AS has its business address in Nedenes.

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.