BIZTRAC BETA
Construction of residential and non-residential buildings

BOH19 AS

Org. no. 923157832 Limited company (AS) Kongsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 1.7m
Equity NOK 3.4m
Incorporated 2019
Share capital NOK 30,000

BOH19 AS is registered as a limited company in Kongsberg, Buskerud with organisation number 923157832. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg, herunder anleggs og bygg ledelse. I dette ligger også utleie av maskiner og redskap med og uten fører. Selskapet kan drive med virksomhet som er naturlig tilgrensende. Selskapet kan samarbeide med andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 1.7m
Equity
NOK 3.4m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns BOH19 AS?

KRISTIAN LINDEM BARLINDHAUG
BOH19 AS
NOK 3.9m rev. · NOK 1.7m profit

BOH19 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOH19 AS

Who owns BOH19 AS?

KRISTIAN LINDEM BARLINDHAUG is the largest registered owner, with 100.0%.

What is the revenue of BOH19 AS?

BOH19 AS had revenue of NOK 3.9m in 2024.

Who is the general manager of BOH19 AS?

Ole Einar Høimyr Barlindhaug is registered as general manager of BOH19 AS.

Where is BOH19 AS based?

BOH19 AS has its business address in Kongsberg.

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.