biztrac. BETA
COMPANY REGISTER PROFILE
912119416 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Installation of insulation

BLÅSEISOLASJON AS

Org. no. 912119416 Limited company (AS) Jevnaker Incorporated 2013 Active
Revenue 2025 NOK 2.7m
Operating profit NOK 43,000
Equity NOK 540,000
Incorporated 2013
Employees 6
Share capital NOK 30,000

BLÅSEISOLASJON AS is registered as a limited company in Jevnaker, Akershus with organisation number 912119416. The business is classified under installation of insulation (NACE 43.230). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Byggtekniske arbeider som isolasjon og elektriske installasjoner samt investeringer i andre selskaper og det som følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +24 %
Operating profit
NOK 43,000
▲ +116 %
Equity
NOK 540,000
▲ +8 %
Est. value
NOK 453,000

Financial health · 2025

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
4.6%
Weak
Return on total assets
Solidity
55.6%
Very good
Equity as a share of total capital

Who owns BLÅSEISOLASJON AS?

BLÅSEISOLASJON AS
NOK 2.7m rev. · NOK 43,000 profit

BLÅSEISOLASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLÅSEISOLASJON AS

Who owns BLÅSEISOLASJON AS?

DALA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BLÅSEISOLASJON AS?

BLÅSEISOLASJON AS had revenue of NOK 2.7m in 2025.

Who is the general manager of BLÅSEISOLASJON AS?

Lars Johansen Ås is registered as general manager of BLÅSEISOLASJON AS.

Where is BLÅSEISOLASJON AS based?

BLÅSEISOLASJON AS has its business address in Jevnaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.