BIZTRAC BETA
Construction of residential and non-residential buildings

BJARNASTEIN HOLDING AS

Org. no. 822707742 Limited company (AS) Grimstad Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 4.5m
Incorporated 2019
Share capital NOK 50,000

Signals

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

BJARNASTEIN HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 822707742. 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 50,000, divided into 100 shares. The company's stated purpose is: “Selskapet er et holdingselskap og kan ha eierandeler i andre selskaper samt at det kan bistå andre selskaper med styre- og ledelsesverv. I tillegg kan selskapet drive rådgivende virksomhet innenfor bygg- og annleggsbransjen, samt tilknytta tjenester.”.

Key figures · 2024

Operating profit
NOK −14,000
Equity
NOK 4.5m
Est. value
NOK 11.9m

Financial health · 2024

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

Who owns BJARNASTEIN HOLDING AS?

PETTER BJARNASTEIN
BJARNASTEIN HOLDING AS
· NOK −14,000 profit

BJARNASTEIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJARNASTEIN HOLDING AS own?

BJARNASTEIN HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

BJARNASTEIN HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about BJARNASTEIN HOLDING AS

Who owns BJARNASTEIN HOLDING AS?

PETTER BJARNASTEIN is the largest registered owner, with 100.0%.

Where is BJARNASTEIN HOLDING AS based?

BJARNASTEIN HOLDING AS has its business address in Grimstad.

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.