BIZTRAC BETA
Growing of other non-perennial crops

KRYDDERGARDEN AS

Org. no. 932574152 Limited company (AS) Klepp Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK −285,000
Equity NOK 1.4m
Incorporated 2023
Employees 15
Share capital NOK 100,000

Signals

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

KRYDDERGARDEN AS is registered as a limited company in Klepp, Rogaland with organisation number 932574152. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2023 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Gartnerivirksomhet, med hovedvekt på produksjon av tomater og urter, samt annen virksomhet som naturlig kan knyttes til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK −285,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK −285,000
Equity
NOK 1.4m
Est. value
NOK 7.9m

Financial health · 2025

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

Who owns KRYDDERGARDEN AS?

ROGER LIMA
KRYDDERGARDEN AS
NOK 12.9m rev. · NOK −285,000 profit

KRYDDERGARDEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRYDDERGARDEN AS

Who owns KRYDDERGARDEN AS?

ROGER LIMA is the largest registered owner, with 50.0%.

What is the revenue of KRYDDERGARDEN AS?

KRYDDERGARDEN AS had revenue of NOK 12.9m in 2025.

Who is the general manager of KRYDDERGARDEN AS?

Beathe Horpestad is registered as general manager of KRYDDERGARDEN AS.

Where is KRYDDERGARDEN AS based?

KRYDDERGARDEN AS has its business address in Kleppe.

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.