BIZTRAC BETA
Rental and operating of own or leased real estate

BIRKELAND GRUPPEN AS

Org. no. 997497376 Limited company (AS) Austevoll Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −2.9m
Equity NOK 114.0m
Incorporated 2011
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BIRKELAND GRUPPEN AS is registered as a limited company in Austevoll, Vestland with organisation number 997497376. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Å eie aksjer og investere i andre selskap, herunder maritime næringer, samt alt hva hermed står i forbindelse. Videre skal selskapet drive med investering i fast eiendom.”.

Key figures · 2024

Operating profit
NOK −2.9m
Equity
NOK 114.0m
Est. value
NOK 104.0m

Financial health · 2024

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

Who owns BIRKELAND GRUPPEN AS?

ASTBI AS
BIRKELAND GRUPPEN AS
· NOK −2.9m profit

BIRKELAND GRUPPEN AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BIRKELAND GRUPPEN AS own?

BIRKELAND GRUPPEN AS holds stakes in 10 companies:

See the full ownership structure →

Group structure

BIRKELAND GRUPPEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about BIRKELAND GRUPPEN AS

Who owns BIRKELAND GRUPPEN AS?

ASTBI AS is the largest registered owner, with 36.4%.

Where is BIRKELAND GRUPPEN AS based?

BIRKELAND GRUPPEN AS has its business address in Storebø.

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.