biztrac. BETA
COMPANY REGISTER PROFILE
918518444 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other new goods

BR HAUKLAND AS

Org. no. 918518444 Limited company (AS) Kongsberg Incorporated 2017 Active
Revenue 2025 NOK 829,000
Operating profit NOK −130,000
Equity NOK 26,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

BR HAUKLAND AS is registered as a limited company in Kongsberg, Buskerud with organisation number 918518444. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Utleie av arbeidskraft, import og salg av hobbyartikler, reparasjon av datamaskiner samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 829,000 in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 829,000
▼ −34 %
Operating profit
NOK −130,000
▲ +13 %
Equity
NOK 26,000
▼ −84 %
Est. value
NOK 213,000

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
-22.7%
Not satisfactory
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BR HAUKLAND AS?

BR HAUKLAND AS
NOK 829,000 rev. · NOK −130,000 profit

BR HAUKLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BR HAUKLAND AS

Who owns BR HAUKLAND AS?

Roar Haukland is the largest registered owner, with 100.0%.

What is the revenue of BR HAUKLAND AS?

BR HAUKLAND AS had revenue of NOK 829,000 in 2025.

Where is BR HAUKLAND AS based?

BR HAUKLAND 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 03.10.2026.

Report a problem

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