BIZTRAC BETA
Rental and operating of own or leased real estate

EKEN EIENDOM AS

Org. no. 990379173 Limited company (AS) Drammen Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 754,000
Operating profit NOK 273,000
Equity NOK 7.5m
Incorporated 2006
Share capital NOK 200,000

EKEN EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 990379173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom, samt alt som står i forbindelse med dette herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 754,000 in revenue and NOK 273,000 in operating profit.

Key figures · 2025

Revenue
NOK 754,000
Operating profit
NOK 273,000
Equity
NOK 7.5m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns EKEN EIENDOM AS?

FREDRIK EKEN
EKEN EIENDOM AS
NOK 754,000 rev. · NOK 273,000 profit

EKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EKEN EIENDOM AS own?

EKEN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EKEN EIENDOM AS

Who owns EKEN EIENDOM AS?

FREDRIK EKEN is the largest registered owner, with 100.0%.

What is the revenue of EKEN EIENDOM AS?

EKEN EIENDOM AS had revenue of NOK 754,000 in 2025.

Who is the general manager of EKEN EIENDOM AS?

Fredrik Eken is registered as general manager of EKEN EIENDOM AS.

Where is EKEN EIENDOM AS based?

EKEN EIENDOM AS has its business address in Drammen.

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.