BIZTRAC BETA
Other captive investment companies

TROMMENATTEN INVEST AS

Org. no. 994961551 Limited company (AS) Asker Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.4m
Equity NOK 5.1m
Incorporated 2009
Share capital NOK 600,000

TROMMENATTEN INVEST AS is registered as a limited company in Asker, Akershus with organisation number 994961551. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2009. Registered share capital is NOK 600,000, divided into 600100 shares. The company's stated purpose is: “Investere i aksjer og andre formuesobjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.4m
Equity
NOK 5.1m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns TROMMENATTEN INVEST AS?

BJØRN ERIK DAHL
TROMMENATTEN INVEST AS
NOK 2.7m rev. · NOK 1.4m profit

TROMMENATTEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TROMMENATTEN INVEST AS own?

TROMMENATTEN INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TROMMENATTEN INVEST AS

Who owns TROMMENATTEN INVEST AS?

BJØRN ERIK DAHL is the largest registered owner, with 100.0%.

What is the revenue of TROMMENATTEN INVEST AS?

TROMMENATTEN INVEST AS had revenue of NOK 2.7m in 2024.

Who is the general manager of TROMMENATTEN INVEST AS?

Bjørn Erik Dahl is registered as general manager of TROMMENATTEN INVEST AS.

Where is TROMMENATTEN INVEST AS based?

TROMMENATTEN INVEST AS has its business address in Asker.

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.