BIZTRAC BETA
Landscape service activities

BÆRUM HAGESERVICE AS

Org. no. 813766132 Limited company (AS) Ringerike Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 94,000
Equity NOK 65,000
Incorporated 2014
Share capital NOK 30,000

BÆRUM HAGESERVICE AS is registered as a limited company in Ringerike, Buskerud with organisation number 813766132. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggsgartnervirksomhet, vaktmestertjenester, service-tjenester, handelsvirksomhet samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 94,000
Equity
NOK 65,000
Est. value
NOK 361,000

Financial health · 2024

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

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

Who owns BÆRUM HAGESERVICE AS?

JAN MIKAEL SKJÆGGESTAD
BÆRUM HAGESERVICE AS
NOK 2.3m rev. · NOK 94,000 profit

BÆRUM HAGESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÆRUM HAGESERVICE AS

Who owns BÆRUM HAGESERVICE AS?

JAN MIKAEL SKJÆGGESTAD is the largest registered owner, with 100.0%.

What is the revenue of BÆRUM HAGESERVICE AS?

BÆRUM HAGESERVICE AS had revenue of NOK 2.3m in 2025.

Who is the general manager of BÆRUM HAGESERVICE AS?

Jan Mikael Skjæggestad is registered as general manager of BÆRUM HAGESERVICE AS.

Where is BÆRUM HAGESERVICE AS based?

BÆRUM HAGESERVICE AS has its business address in Hønefoss.

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.