BIZTRAC BETA
Rental and operating of own or leased real estate

ØSTREM EIENDOM III AS

Org. no. 922656371 Limited company (AS) Karmøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.2m
Equity NOK 9.6m
Incorporated 2019
Share capital NOK 4.8m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ØSTREM EIENDOM III AS is registered as a limited company in Karmøy, Rogaland with organisation number 922656371. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 4.8m, divided into 300 shares. The company's stated purpose is: “Eiendomsselskap hvis virksomhet utelukkende består i å eie fast eiendom og drift av disse. Selskapet kan også eie aksjer eller andeler i andre eiendomsselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.2m
Equity
NOK 9.6m
Est. value
NOK 8.9m

Financial health · 2025

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

Who owns ØSTREM EIENDOM III AS?

GOD DRIV UKO AS
ØSTREM EIENDOM III AS
NOK 1.8m rev. · NOK 1.2m profit

ØSTREM EIENDOM III AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTREM EIENDOM III AS

Who owns ØSTREM EIENDOM III AS?

GOD DRIV UKO AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTREM EIENDOM III AS?

ØSTREM EIENDOM III AS had revenue of NOK 1.8m in 2025.

Where is ØSTREM EIENDOM III AS based?

ØSTREM EIENDOM III AS has its business address in Kopervik.

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.