BIZTRAC BETA
Construction of residential and non-residential buildings

IHLE PROSJEKT AS

Org. no. 998740118 Limited company (AS) Nannestad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 505,000
Equity NOK 5.2m
Incorporated 2012
Share capital NOK 30,000

IHLE PROSJEKT AS is registered as a limited company in Nannestad, Akershus with organisation number 998740118. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer, utbygging av boliger og boligområder og dertilhørende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 505,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 505,000
Equity
NOK 5.2m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns IHLE PROSJEKT AS?

MONICA STOKKER LANGHELLE
IHLE PROSJEKT AS
NOK 0 rev. · NOK 505,000 profit

IHLE PROSJEKT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does IHLE PROSJEKT AS own?

IHLE PROSJEKT AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about IHLE PROSJEKT AS

Who owns IHLE PROSJEKT AS?

MONICA STOKKER LANGHELLE is the largest registered owner, with 50.0%.

What is the revenue of IHLE PROSJEKT AS?

IHLE PROSJEKT AS had revenue of NOK 0 in 2025.

Who is the general manager of IHLE PROSJEKT AS?

Petter Fossum Langhelle is registered as general manager of IHLE PROSJEKT AS.

Where is IHLE PROSJEKT AS based?

IHLE PROSJEKT AS has its business address in Nannestad.

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.