BIZTRAC BETA
Support services to forestry

JM AASEN AS

Org. no. 931840827 Limited company (AS) Ørsta Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 762,000
Operating profit NOK 3,000
Equity NOK −11,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).

JM AASEN AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 931840827. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen skogbruk og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 762,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 762,000
Operating profit
NOK 3,000
Equity
NOK −11,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns JM AASEN AS?

JM AASEN HOLDING AS
JM AASEN AS
NOK 762,000 rev. · NOK 3,000 profit

JM AASEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JM AASEN AS

Who owns JM AASEN AS?

JM AASEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JM AASEN AS?

JM AASEN AS had revenue of NOK 762,000 in 2025.

Who is the general manager of JM AASEN AS?

Jon Magne Aasen is registered as general manager of JM AASEN AS.

Where is JM AASEN AS based?

JM AASEN AS has its business address in Ørsta.

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.