BIZTRAC BETA
Rental and operating of own or leased real estate

LØWENSTRASSE EIENDOM AS

Org. no. 988942499 Limited company (AS) Strand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 13.8m
Operating profit NOK 11.3m
Equity NOK 47.0m
Incorporated 2005
Share capital NOK 2.0m

Signals

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

LØWENSTRASSE EIENDOM AS is registered as a limited company in Strand, Rogaland with organisation number 988942499. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.0m, divided into 250 shares. The company's stated purpose is: “Å investere og eie fast eiendom eller selskapet som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.8m in revenue and NOK 11.3m in operating profit.

Key figures · 2025

Revenue
NOK 13.8m
Operating profit
NOK 11.3m
Equity
NOK 47.0m
Est. value
NOK 54.6m

Financial health · 2025

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

Who owns LØWENSTRASSE EIENDOM AS?

SVANHOLMEN LAGERBYGG AS
LØWENSTRASSE EIENDOM AS
NOK 13.8m rev. · NOK 11.3m profit

LØWENSTRASSE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØWENSTRASSE EIENDOM AS

Who owns LØWENSTRASSE EIENDOM AS?

SVANHOLMEN LAGERBYGG AS is the largest registered owner, with 100.0%.

What is the revenue of LØWENSTRASSE EIENDOM AS?

LØWENSTRASSE EIENDOM AS had revenue of NOK 13.8m in 2025.

Where is LØWENSTRASSE EIENDOM AS based?

LØWENSTRASSE EIENDOM AS has its business address in Tau.

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.