BIZTRAC BETA
Landscape service activities

GRØTEIG AS

Org. no. 916508816 Limited company (AS) Horten Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 63.6m
Operating profit NOK −1.1m
Equity NOK 12.8m
Incorporated 2015
Employees 38
Share capital NOK 4.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

GRØTEIG AS is registered as a limited company in Horten, Vestfold with organisation number 916508816. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2015 and has 38 registered employees. Registered share capital is NOK 4.0m, divided into 300 shares. The company's stated purpose is: “Anleggsgartnervirksomhet, samt alt som står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 63.6m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 63.6m
Operating profit
NOK −1.1m
Equity
NOK 12.8m
Est. value
NOK 46.7m

Financial health · 2024

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.3%
Very good
Equity as a share of total capital

Who owns GRØTEIG AS?

HÅKONSEN OG SUKKE LANDSKAPSENTREPRENØR AS
GRØTEIG AS
NOK 63.6m rev. · NOK −1.1m profit

GRØTEIG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GRØTEIG AS own?

GRØTEIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GRØTEIG AS

Who owns GRØTEIG AS?

HÅKONSEN OG SUKKE LANDSKAPSENTREPRENØR AS is the largest registered owner, with 34.0%.

What is the revenue of GRØTEIG AS?

GRØTEIG AS had revenue of NOK 63.6m in 2024.

Who is the general manager of GRØTEIG AS?

Sindre Book is registered as general manager of GRØTEIG AS.

Where is GRØTEIG AS based?

GRØTEIG AS has its business address in Nykirke.

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.