BIZTRAC BETA
Ventilation installation

K. NILSEN BOLIGVENTILASJON AS

Org. no. 928467791 Limited company (AS) Øygarden Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 17,000
Equity NOK 235,000
Incorporated 2021
Share capital NOK 39,000

K. NILSEN BOLIGVENTILASJON AS is registered as a limited company in Øygarden, Vestland with organisation number 928467791. The business is classified under ventilation installation (NACE 43.223). The company was incorporated in 2021. Registered share capital is NOK 39,000, divided into 30 shares. The company's stated purpose is: “Salg, prosjektering, service og montering av ventilasjonsanlegg, samt det som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 17,000
Equity
NOK 235,000
Est. value
NOK 159,000

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.6%
Good
Equity as a share of total capital

Who owns K. NILSEN BOLIGVENTILASJON AS?

KJETIL EUGEN NILSEN
K. NILSEN BOLIGVENTILASJON AS
NOK 2.8m rev. · NOK 17,000 profit

K. NILSEN BOLIGVENTILASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K. NILSEN BOLIGVENTILASJON AS

Who owns K. NILSEN BOLIGVENTILASJON AS?

KJETIL EUGEN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of K. NILSEN BOLIGVENTILASJON AS?

K. NILSEN BOLIGVENTILASJON AS had revenue of NOK 2.8m in 2025.

Where is K. NILSEN BOLIGVENTILASJON AS based?

K. NILSEN BOLIGVENTILASJON AS has its business address in Straume.

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.