BIZTRAC BETA
Other captive investment companies

FLÅHAMMER HOLDING AS

Org. no. 915879721 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Equity NOK 20,000
Incorporated 2015
Share capital NOK 30,000

FLÅHAMMER HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915879721. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og verdipapirer samt eierskap og investering i andre foretak og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”.

Key figures · 2024

Equity
NOK 20,000
Est. value
NOK 18,000

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FLÅHAMMER HOLDING AS?

BEN MICHAEL FLÅHAMMER
FLÅHAMMER HOLDING AS

FLÅHAMMER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLÅHAMMER HOLDING AS own?

FLÅHAMMER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLÅHAMMER HOLDING AS

Who owns FLÅHAMMER HOLDING AS?

BEN MICHAEL FLÅHAMMER is the largest registered owner, with 100.0%.

Who is the general manager of FLÅHAMMER HOLDING AS?

Ben Michael Flåhammer is registered as general manager of FLÅHAMMER HOLDING AS.

Where is FLÅHAMMER HOLDING AS based?

FLÅHAMMER HOLDING AS has its business address in Tiller.

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.