BIZTRAC BETA
Rental and operating of own or leased real estate

JMA DAHLEN HOLDING AS

Org. no. 917556318 Limited company (AS) Levanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 144,000
Operating profit NOK 80,000
Equity NOK 10.3m
Incorporated 2016
Share capital NOK 30,000

JMA DAHLEN HOLDING AS is registered as a limited company in Levanger, Trøndelag with organisation number 917556318. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer, andeler og fast eiendom, samt virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 144,000 in revenue and NOK 80,000 in operating profit.

Key figures · 2024

Revenue
NOK 144,000
Operating profit
NOK 80,000
Equity
NOK 10.3m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns JMA DAHLEN HOLDING AS?

JAN MARTIN ALBERTSEN DAHLEN
JMA DAHLEN HOLDING AS
NOK 144,000 rev. · NOK 80,000 profit

JMA DAHLEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JMA DAHLEN HOLDING AS own?

JMA DAHLEN HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about JMA DAHLEN HOLDING AS

Who owns JMA DAHLEN HOLDING AS?

JAN MARTIN ALBERTSEN DAHLEN is the largest registered owner, with 100.0%.

What is the revenue of JMA DAHLEN HOLDING AS?

JMA DAHLEN HOLDING AS had revenue of NOK 144,000 in 2024.

Where is JMA DAHLEN HOLDING AS based?

JMA DAHLEN HOLDING AS has its business address in Ekne.

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.