BIZTRAC BETA
Rental and operating of own or leased real estate

OLEKI AS

Org. no. 986401121 Limited company (AS) Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 582,000
Equity NOK 47.1m
Incorporated 2003
Share capital NOK 30,000

OLEKI AS is registered as a limited company in Hå, Rogaland with organisation number 986401121. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utbygging, kjøp og salg. Entreprenørvirksomhet herunder utleie, kjøp og salg av varer og utstyr. I tillegg til dette kjøp og salg av aksjer og eierandeler i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 582,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 582,000
Equity
NOK 47.1m
Est. value
NOK 34.1m

Financial health · 2024

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

Who owns OLEKI AS?

OLE KRISTIAN INGEBRETHSEN
OLEKI AS
NOK 1.3m rev. · NOK 582,000 profit

OLEKI AS has 6 registered shareholders:

All shareholders and roles →

Which companies does OLEKI AS own?

OLEKI AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about OLEKI AS

Who owns OLEKI AS?

OLE KRISTIAN INGEBRETHSEN is the largest registered owner, with 35.0%.

What is the revenue of OLEKI AS?

OLEKI AS had revenue of NOK 1.3m in 2024.

Who is the general manager of OLEKI AS?

Asle Ingebrethsen is registered as general manager of OLEKI AS.

Where is OLEKI AS based?

OLEKI AS has its business address in Brusand.

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.