BIZTRAC BETA
Other captive investment companies

FLAGSTONE AS

Org. no. 984825188 Limited company (AS) Bærum Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −277,000
Equity NOK 12.9m
Incorporated 2002
Share capital NOK 108,000

Signals

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

FLAGSTONE AS is registered as a limited company in Bærum, Akershus with organisation number 984825188. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2002. Registered share capital is NOK 108,000, divided into 54 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, samt rådgivning og konsulenttjenester innen fagområder selskapet besitter kompetanse på Selskapet kan drive forretninger med "gearede" produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −277,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −277,000
Equity
NOK 12.9m
Est. value
NOK 16.6m

Financial health · 2024

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

Who owns FLAGSTONE AS?

HELLE ENGELHART TUNGESVIK
FLAGSTONE AS
NOK 0 rev. · NOK −277,000 profit

FLAGSTONE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FLAGSTONE AS own?

FLAGSTONE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FLAGSTONE AS

Who owns FLAGSTONE AS?

HELLE ENGELHART TUNGESVIK is the largest registered owner, with 29.6%.

What is the revenue of FLAGSTONE AS?

FLAGSTONE AS had revenue of NOK 0 in 2024.

Where is FLAGSTONE AS based?

FLAGSTONE AS has its business address in Slependen.

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.