BIZTRAC BETA
Development of building projects

ESPM AS

Org. no. 996165167 Limited company (AS) Kristiansand Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 183,000
Operating profit NOK −115,000
Equity NOK 38.6m
Incorporated 2010
Share capital NOK 109,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−115k kr).

ESPM AS is registered as a limited company in Kristiansand, Agder with organisation number 996165167. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. Registered share capital is NOK 109,000, divided into 18 shares. The company's stated purpose is: “Holdingselskap, eiendomsutvikling, investeringsvirksomhet av enhver art, og alt som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 183,000 in revenue and NOK −115,000 in operating profit.

Key figures · 2025

Revenue
NOK 183,000
Operating profit
NOK −115,000
Equity
NOK 38.6m
Est. value
NOK 44.4m

Financial health · 2025

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

Who owns ESPM AS?

SIRI PEDERSEN MYHRE
ESPM AS
NOK 183,000 rev. · NOK −115,000 profit

ESPM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ESPM AS own?

ESPM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about ESPM AS

Who owns ESPM AS?

SIRI PEDERSEN MYHRE is the largest registered owner, with 50.0%.

What is the revenue of ESPM AS?

ESPM AS had revenue of NOK 183,000 in 2025.

Who is the general manager of ESPM AS?

Eivind Stoud Platou Myhre is registered as general manager of ESPM AS.

Where is ESPM AS based?

ESPM AS has its business address in Kristiansand S.

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.