BIZTRAC BETA
Buying and selling of own real estate

CUBA EIENDOMSINVEST AS

Org. no. 987661305 Limited company (AS) Stavanger Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 175,000
Operating profit NOK 142,000
Equity NOK 12.6m
Incorporated 2004
Share capital NOK 30,000

CUBA EIENDOMSINVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 987661305. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2004. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt å delta som aksjonær i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 175,000 in revenue and NOK 142,000 in operating profit.

Key figures · 2025

Revenue
NOK 175,000
Operating profit
NOK 142,000
Equity
NOK 12.6m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns CUBA EIENDOMSINVEST AS?

SIV GUNNI EMMERHOFF BORGERSEN
CUBA EIENDOMSINVEST AS
NOK 175,000 rev. · NOK 142,000 profit

CUBA EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CUBA EIENDOMSINVEST AS own?

CUBA EIENDOMSINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CUBA EIENDOMSINVEST AS

Who owns CUBA EIENDOMSINVEST AS?

SIV GUNNI EMMERHOFF BORGERSEN is the largest registered owner, with 100.0%.

What is the revenue of CUBA EIENDOMSINVEST AS?

CUBA EIENDOMSINVEST AS had revenue of NOK 175,000 in 2025.

Where is CUBA EIENDOMSINVEST AS based?

CUBA EIENDOMSINVEST AS has its business address in Stavanger.

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.