BIZTRAC BETA
Landscape service activities

WELDE HAGESERVICE AS

Org. no. 930104310 Limited company (AS) Inderøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −136,000
Equity NOK 222,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

WELDE HAGESERVICE AS is registered as a limited company in Inderøy, Trøndelag with organisation number 930104310. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Anleggsgartnertjenester, hageservice og lignende som naturlig faller sammen med dette, herunder også delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −136,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −136,000
Equity
NOK 222,000
Est. value
NOK 963,000

Financial health · 2025

Liquidity
0.86
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.0%
Good
Equity as a share of total capital

Who owns WELDE HAGESERVICE AS?

MAGNUS WELDE
WELDE HAGESERVICE AS
NOK 1.3m rev. · NOK −136,000 profit

WELDE HAGESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WELDE HAGESERVICE AS

Who owns WELDE HAGESERVICE AS?

MAGNUS WELDE is the largest registered owner, with 100.0%.

What is the revenue of WELDE HAGESERVICE AS?

WELDE HAGESERVICE AS had revenue of NOK 1.3m in 2025.

Who is the general manager of WELDE HAGESERVICE AS?

Magnus Welde is registered as general manager of WELDE HAGESERVICE AS.

Where is WELDE HAGESERVICE AS based?

WELDE HAGESERVICE AS has its business address in Inderøy.

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.