BIZTRAC BETA
Architectural activities

JMN PLAN OG ARKITEKTUR AS

Org. no. 997335953 Limited company (AS) Askøy Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK 1.8m
Equity NOK 129,000
Incorporated 2011
Employees 8
Share capital NOK 100,000

JMN PLAN OG ARKITEKTUR AS is registered as a limited company in Askøy, Vestland with organisation number 997335953. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2011 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive rådgivende arkitektvirksomhet, investeringer og deltakelse i andre selskap og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK 1.8m
Equity
NOK 129,000
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns JMN PLAN OG ARKITEKTUR AS?

OLE DALEHAUG HOLDING AS
JMN PLAN OG ARKITEKTUR AS
NOK 8.8m rev. · NOK 1.8m profit

JMN PLAN OG ARKITEKTUR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JMN PLAN OG ARKITEKTUR AS

Who owns JMN PLAN OG ARKITEKTUR AS?

OLE DALEHAUG HOLDING AS is the largest registered owner, with 67.0%.

What is the revenue of JMN PLAN OG ARKITEKTUR AS?

JMN PLAN OG ARKITEKTUR AS had revenue of NOK 8.8m in 2024.

Who is the general manager of JMN PLAN OG ARKITEKTUR AS?

Ole Kristian Dalehaug is registered as general manager of JMN PLAN OG ARKITEKTUR AS.

Where is JMN PLAN OG ARKITEKTUR AS based?

JMN PLAN OG ARKITEKTUR AS has its business address in Kleppestø.

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.