BIZTRAC BETA
Rental and operating of own or leased real estate

STRAUME EIENDOMSSELSKAP AS

Org. no. 839666942 Limited company (AS) Øygarden Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 16.7m
Operating profit NOK 11.7m
Equity NOK 48.3m
Incorporated 1986
Share capital NOK 500,000

STRAUME EIENDOMSSELSKAP AS is registered as a limited company in Øygarden, Vestland with organisation number 839666942. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 500,000. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.7m in revenue and NOK 11.7m in operating profit.

Key figures · 2024

Revenue
NOK 16.7m
Operating profit
NOK 11.7m
Equity
NOK 48.3m
Est. value
NOK 58.6m

Financial health · 2024

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

Who owns STRAUME EIENDOMSSELSKAP AS?

GOBO NÆRING AS
STRAUME EIENDOMSSELSKAP AS
NOK 16.7m rev. · NOK 11.7m profit

STRAUME EIENDOMSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRAUME EIENDOMSSELSKAP AS

Who owns STRAUME EIENDOMSSELSKAP AS?

GOBO NÆRING AS is the largest registered owner, with 100.0%.

What is the revenue of STRAUME EIENDOMSSELSKAP AS?

STRAUME EIENDOMSSELSKAP AS had revenue of NOK 16.7m in 2024.

Who is the general manager of STRAUME EIENDOMSSELSKAP AS?

Frank Lægreid is registered as general manager of STRAUME EIENDOMSSELSKAP AS.

Where is STRAUME EIENDOMSSELSKAP AS based?

STRAUME EIENDOMSSELSKAP AS has its business address in Knarrevik.

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.