BIZTRAC BETA
Buying and selling of own real estate

LØVENVOLD THEATER EIENDOM AS

Org. no. 929249844 Limited company (AS) Ålesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −97,000
Equity NOK 4.8m
Incorporated 2022
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−97k kr).

LØVENVOLD THEATER EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 929249844. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendom, forretningsutvikling og eiendomsforvaltning og dertil forbunden virksomhet, herunder investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −97,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −97,000
Equity
NOK 4.8m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns LØVENVOLD THEATER EIENDOM AS?

BRØDRENE JANGAARD AS
LØVENVOLD THEATER EIENDOM AS
NOK 1.4m rev. · NOK −97,000 profit

LØVENVOLD THEATER EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØVENVOLD THEATER EIENDOM AS

Who owns LØVENVOLD THEATER EIENDOM AS?

BRØDRENE JANGAARD AS is the largest registered owner, with 50.0%.

What is the revenue of LØVENVOLD THEATER EIENDOM AS?

LØVENVOLD THEATER EIENDOM AS had revenue of NOK 1.4m in 2024.

Where is LØVENVOLD THEATER EIENDOM AS based?

LØVENVOLD THEATER EIENDOM AS has its business address in Ålesund.

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.