BIZTRAC BETA
Landscape service activities

HØSTMARK LØVE HOLDING AS

Org. no. 825833722 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −64,000
Equity NOK 3.5m
Incorporated 2020
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−64k kr).

HØSTMARK LØVE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 825833722. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2020. Registered share capital is NOK 80,000, divided into 40000 shares. The company's stated purpose is: “Eie aksjer og andeler i ulike selskaper knyttet til eiendom, landskapstjenester og øvrige selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −64,000
Equity
NOK 3.5m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns HØSTMARK LØVE HOLDING AS?

ERIK HØSTMARK LØVE
HØSTMARK LØVE HOLDING AS
NOK 0 rev. · NOK −64,000 profit

HØSTMARK LØVE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HØSTMARK LØVE HOLDING AS own?

HØSTMARK LØVE HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about HØSTMARK LØVE HOLDING AS

Who owns HØSTMARK LØVE HOLDING AS?

ERIK HØSTMARK LØVE is the largest registered owner, with 100.0%.

What is the revenue of HØSTMARK LØVE HOLDING AS?

HØSTMARK LØVE HOLDING AS had revenue of NOK 0 in 2025.

Where is HØSTMARK LØVE HOLDING AS based?

HØSTMARK LØVE HOLDING AS has its business address in Oslo.

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.