BIZTRAC BETA
Landscape service activities

LANDSKAPSMESTEREN AS

Org. no. 925923257 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 26.2m
Operating profit NOK 2.3m
Equity NOK 2.7m
Incorporated 2020
Employees 20
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-05-21 Adresseendring registrert 2026-05-21.

LANDSKAPSMESTEREN AS is registered as a limited company in Oslo, Oslo with organisation number 925923257. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2020 and has 20 registered employees. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Gartnertjenester, håndtverkstjenester, utleie av maskiner samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.2m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 26.2m
Operating profit
NOK 2.3m
Equity
NOK 2.7m
Est. value
NOK 10.4m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.1%
Good
Equity as a share of total capital

Who owns LANDSKAPSMESTEREN AS?

HØSTMARK LØVE HOLDING AS
LANDSKAPSMESTEREN AS
NOK 26.2m rev. · NOK 2.3m profit

LANDSKAPSMESTEREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANDSKAPSMESTEREN AS

Who owns LANDSKAPSMESTEREN AS?

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

What is the revenue of LANDSKAPSMESTEREN AS?

LANDSKAPSMESTEREN AS had revenue of NOK 26.2m in 2025.

Who is the general manager of LANDSKAPSMESTEREN AS?

Erik Høstmark Løve is registered as general manager of LANDSKAPSMESTEREN AS.

Where is LANDSKAPSMESTEREN AS based?

LANDSKAPSMESTEREN 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.