BIZTRAC BETA
Rental and operating of own or leased real estate

EPRO HOLDING AS

Org. no. 929295293 Limited company (AS) Enebakk Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK 41,000
Equity NOK 101,000
Incorporated 2022
Share capital NOK 90,000

EPRO HOLDING AS is registered as a limited company in Enebakk, Akershus with organisation number 929295293. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 90,000, divided into 10 shares. The company's stated purpose is: “Forvaltning av eierinteresser, drift av datterselskaper og det som måtte stå i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK 41,000
Equity
NOK 101,000
Est. value
NOK 160,000

Financial health · 2024

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

Who owns EPRO HOLDING AS?

ENEBAKK KOMMUNE
EPRO HOLDING AS
NOK 60,000 rev. · NOK 41,000 profit

EPRO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EPRO HOLDING AS own?

EPRO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EPRO HOLDING AS

Who owns EPRO HOLDING AS?

ENEBAKK KOMMUNE is the largest registered owner, with 100.0%.

What is the revenue of EPRO HOLDING AS?

EPRO HOLDING AS had revenue of NOK 60,000 in 2024.

Who is the general manager of EPRO HOLDING AS?

Trygve Karlsen is registered as general manager of EPRO HOLDING AS.

Where is EPRO HOLDING AS based?

EPRO HOLDING AS has its business address in Enebakk.

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.