BIZTRAC BETA
Other real estate activities on a fee or contract basis

BHK HOLDING AS

Org. no. 989029487 Limited company (AS) Vestvågøy Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 527,000
Operating profit NOK 489,000
Equity NOK 15.7m
Incorporated 2005
Share capital NOK 1.1m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BHK HOLDING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 989029487. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 1.1m, divided into 1050 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 527,000 in revenue and NOK 489,000 in operating profit.

Key figures · 2025

Revenue
NOK 527,000
Operating profit
NOK 489,000
Equity
NOK 15.7m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns BHK HOLDING AS?

BJØRN HARALD KARLSEN
BHK HOLDING AS
NOK 527,000 rev. · NOK 489,000 profit

BHK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BHK HOLDING AS own?

BHK HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BHK HOLDING AS

Who owns BHK HOLDING AS?

BJØRN HARALD KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of BHK HOLDING AS?

BHK HOLDING AS had revenue of NOK 527,000 in 2025.

Where is BHK HOLDING AS based?

BHK HOLDING AS has its business address in Bøstad.

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.