BIZTRAC BETA
Landscape service activities

HAGEKONSULENTER AS

Org. no. 932950812 Limited company (AS) Sarpsborg Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 821,000
Operating profit NOK −37,000
Equity NOK 65,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

HAGEKONSULENTER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 932950812. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av anleggsgartnertjenester og produkter som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 821,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 821,000
Operating profit
NOK −37,000
Equity
NOK 65,000
Est. value
NOK 553,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAGEKONSULENTER AS?

LUKASZ PUCHALSKI
HAGEKONSULENTER AS
NOK 821,000 rev. · NOK −37,000 profit

HAGEKONSULENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAGEKONSULENTER AS

Who owns HAGEKONSULENTER AS?

LUKASZ PUCHALSKI is the largest registered owner, with 60.0%.

What is the revenue of HAGEKONSULENTER AS?

HAGEKONSULENTER AS had revenue of NOK 821,000 in 2024.

Who is the general manager of HAGEKONSULENTER AS?

Ewa Puchalska is registered as general manager of HAGEKONSULENTER AS.

Where is HAGEKONSULENTER AS based?

HAGEKONSULENTER AS has its business address in Ise.

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.