BIZTRAC BETA
Other captive investment companies

ALLAN BJØRNSTAD HOLDING AS

Org. no. 919871539 Limited company (AS) Lier Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −36,000
Equity NOK 3.4m
Incorporated 2017
Share capital NOK 30,000

Signals

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

ALLAN BJØRNSTAD HOLDING AS is registered as a limited company in Lier, Buskerud with organisation number 919871539. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investeringer i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 3.4m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns ALLAN BJØRNSTAD HOLDING AS?

ALLAN MAURICE BJØRNSTAD
ALLAN BJØRNSTAD HOLDING AS
NOK 0 rev. · NOK −36,000 profit

ALLAN BJØRNSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALLAN BJØRNSTAD HOLDING AS own?

ALLAN BJØRNSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALLAN BJØRNSTAD HOLDING AS

Who owns ALLAN BJØRNSTAD HOLDING AS?

ALLAN MAURICE BJØRNSTAD is the largest registered owner, with 100.0%.

What is the revenue of ALLAN BJØRNSTAD HOLDING AS?

ALLAN BJØRNSTAD HOLDING AS had revenue of NOK 0 in 2025.

Where is ALLAN BJØRNSTAD HOLDING AS based?

ALLAN BJØRNSTAD HOLDING AS has its business address in Tranby.

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.