BIZTRAC BETA
Wholesale of fruit and vegetables

LÅGEN GULROT AS

Org. no. 839658842 Limited company (AS) Larvik Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 178.7m
Operating profit NOK 7.3m
Equity NOK 44.0m
Incorporated 1986
Employees 25
Share capital NOK 133,000

LÅGEN GULROT AS is registered as a limited company in Larvik, Vestfold with organisation number 839658842. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 1986 and has 25 registered employees. Registered share capital is NOK 133,000. The company's stated purpose is: “Omsetning av jordbruksprodukter, det som dermed står i forbindelse, deltagelse i andre selskaper, samt kjøp av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 178.7m in revenue and NOK 7.3m in operating profit.

Key figures · 2024

Revenue
NOK 178.7m
Operating profit
NOK 7.3m
Equity
NOK 44.0m
Est. value
NOK 47.5m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.5%
Very good
Equity as a share of total capital

Who owns LÅGEN GULROT AS?

VINTERSTUA AS
LÅGEN GULROT AS
NOK 178.7m rev. · NOK 7.3m profit

LÅGEN GULROT AS has 14 registered shareholders:

All shareholders and roles →

Which companies does LÅGEN GULROT AS own?

LÅGEN GULROT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LÅGEN GULROT AS

Who owns LÅGEN GULROT AS?

VINTERSTUA AS is the largest registered owner, with 18.8%.

What is the revenue of LÅGEN GULROT AS?

LÅGEN GULROT AS had revenue of NOK 178.7m in 2024.

Who is the general manager of LÅGEN GULROT AS?

Øystein Borg is registered as general manager of LÅGEN GULROT AS.

Where is LÅGEN GULROT AS based?

LÅGEN GULROT AS has its business address in Steinsholt.

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.