BIZTRAC BETA
Activities of tourist offices and destination marketing organisations

IMODALEN AS

Org. no. 822184642 Limited company (AS) Modalen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 101,000
Operating profit NOK 40,000
Equity NOK 56,000
Incorporated 2018
Share capital NOK 62,000

IMODALEN AS is registered as a limited company in Modalen, Vestland with organisation number 822184642. The business is classified under activities of tourist offices and destination marketing organisations (NACE 79.901). The company was incorporated in 2018. Registered share capital is NOK 62,000, divided into 123 shares. The company's stated purpose is: “Salg av utvikling av tjenester og produkter innen reiselivs- og besøksnæringen, samt andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 101,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 101,000
Operating profit
NOK 40,000
Equity
NOK 56,000
Est. value
NOK 162,000

Financial health · 2024

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

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

Who owns IMODALEN AS?

PETTER BENJAMIN ARNESEN
IMODALEN AS
NOK 101,000 rev. · NOK 40,000 profit

IMODALEN AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about IMODALEN AS

Who owns IMODALEN AS?

PETTER BENJAMIN ARNESEN is the largest registered owner, with 12.2%.

What is the revenue of IMODALEN AS?

IMODALEN AS had revenue of NOK 101,000 in 2024.

Who is the general manager of IMODALEN AS?

Simiona Lukaseviciute-Arnesen is registered as general manager of IMODALEN AS.

Where is IMODALEN AS based?

IMODALEN AS has its business address in Modalen.

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.