BIZTRAC BETA
Rental and operating of own or leased real estate

LØW EIENDOM AS

Org. no. 984056389 Limited company (AS) Trondheim Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 806,000
Equity NOK 26.2m
Incorporated 2001
Share capital NOK 1.3m

Signals

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

LØW EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984056389. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 1.3m, divided into 1300 shares. The company's stated purpose is: “Utleie av forretningsbygg og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 806,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 806,000
Equity
NOK 26.2m
Est. value
NOK 19.7m

Financial health · 2024

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

Who owns LØW EIENDOM AS?

GOLH HOLDING AS
LØW EIENDOM AS
NOK 5.3m rev. · NOK 806,000 profit

LØW EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØW EIENDOM AS own?

LØW EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LØW EIENDOM AS

Who owns LØW EIENDOM AS?

GOLH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LØW EIENDOM AS?

LØW EIENDOM AS had revenue of NOK 5.3m in 2024.

Where is LØW EIENDOM AS based?

LØW EIENDOM AS has its business address in Trondheim.

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.