BIZTRAC BETA
Other real estate activities on a fee or contract basis

OEK EIENDOM AS

Org. no. 925577316 Limited company (AS) Klepp Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.2m
Equity NOK 93,000
Incorporated 2020
Share capital NOK 93,000

OEK EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 925577316. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2020. Registered share capital is NOK 93,000, divided into 200 shares. The company's stated purpose is: “Eiendomsforvaltning, herunder drift, utleie, kjøp og salg av fast eiendom, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 1.2m
Equity
NOK 93,000
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OEK EIENDOM AS?

KLINGSHEIM AS
OEK EIENDOM AS
NOK 1.5m rev. · NOK 1.2m profit

OEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OEK EIENDOM AS

Who owns OEK EIENDOM AS?

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

What is the revenue of OEK EIENDOM AS?

OEK EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of OEK EIENDOM AS?

Odd Erling Klingsheim is registered as general manager of OEK EIENDOM AS.

Where is OEK EIENDOM AS based?

OEK EIENDOM AS has its business address in Klepp Stasjon.

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.