BIZTRAC BETA
Rental and operating of own or leased real estate

ØLBERGSTRANDA AS

Org. no. 992591277 Limited company (AS) Time Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 83,000
Operating profit NOK −7,000
Equity NOK −3.4m
Incorporated 2008
Share capital NOK 725,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

ØLBERGSTRANDA AS is registered as a limited company in Time, Rogaland with organisation number 992591277. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 725,000, divided into 1020 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 83,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 83,000
Operating profit
NOK −7,000
Equity
NOK −3.4m

Financial health · 2024

Liquidity
20.23
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-32.1%
Weak
Equity as a share of total capital

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

Who owns ØLBERGSTRANDA AS?

EL - AUTOMATION AS
ØLBERGSTRANDA AS
NOK 83,000 rev. · NOK −7,000 profit

ØLBERGSTRANDA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØLBERGSTRANDA AS

Who owns ØLBERGSTRANDA AS?

EL - AUTOMATION AS is the largest registered owner, with 50.0%.

What is the revenue of ØLBERGSTRANDA AS?

ØLBERGSTRANDA AS had revenue of NOK 83,000 in 2024.

Who is the general manager of ØLBERGSTRANDA AS?

Per Kverneland is registered as general manager of ØLBERGSTRANDA AS.

Where is ØLBERGSTRANDA AS based?

ØLBERGSTRANDA AS has its business address in Kvernaland.

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.