BIZTRAC BETA
Uoppgitt

BJØRKESTAD HOLDING AS

Org. no. 928303594 Limited company (AS) Tromsø Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 1.9m
Incorporated 2021
Share capital NOK 578,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

BJØRKESTAD HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 928303594. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 578,000, divided into 567 shares. The company's stated purpose is: “Investering i aksjer i andre selskaper og aktiviteter som faller naturlig inn under dette. Selskapet kan benytte seg av handel med finansielle instrumenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 1.9m
Est. value
NOK 9.7m

Financial health · 2024

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

Who owns BJØRKESTAD HOLDING AS?

JØRN ESPEN BJØRKESTAD
BJØRKESTAD HOLDING AS
NOK 0 rev. · NOK −7,000 profit

BJØRKESTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRKESTAD HOLDING AS own?

BJØRKESTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRKESTAD HOLDING AS

Who owns BJØRKESTAD HOLDING AS?

JØRN ESPEN BJØRKESTAD is the largest registered owner, with 100.0%.

What is the revenue of BJØRKESTAD HOLDING AS?

BJØRKESTAD HOLDING AS had revenue of NOK 0 in 2024.

Where is BJØRKESTAD HOLDING AS based?

BJØRKESTAD HOLDING AS has its business address in Kvaløya.

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.