BIZTRAC BETA
Rental and operating of own or leased real estate

ESPENES EIENDOM AS

Org. no. 979390424 Limited company (AS) Klepp Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 1.2m
Equity NOK 7.1m
Incorporated 1997
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ESPENES EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 979390424. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 200,000, divided into 20 shares. The company's stated purpose is: “Kjøp og utleie av fast eiendom samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 1.2m
Equity
NOK 7.1m
Est. value
NOK 7.0m

Financial health · 2025

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

Who owns ESPENES EIENDOM AS?

SYNTEMA AS
ESPENES EIENDOM AS
NOK 1.3m rev. · NOK 1.2m profit

ESPENES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESPENES EIENDOM AS

Who owns ESPENES EIENDOM AS?

SYNTEMA AS is the largest registered owner, with 100.0%.

What is the revenue of ESPENES EIENDOM AS?

ESPENES EIENDOM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of ESPENES EIENDOM AS?

Egil Torgersen is registered as general manager of ESPENES EIENDOM AS.

Where is ESPENES EIENDOM AS based?

ESPENES EIENDOM AS has its business address in Kleppe.

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.