BIZTRAC BETA
Growing of other non-perennial crops

LUNDEBY GARTNERI AS

Org. no. 928825809 Limited company (AS) Råde Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 2,000
Equity NOK 45,000
Incorporated 2022
Employees 10
Share capital NOK 30,000

LUNDEBY GARTNERI AS is registered as a limited company in Råde, Østfold with organisation number 928825809. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2022 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av gartnerivirksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK 2,000
Equity
NOK 45,000
Est. value
NOK 30,000

Financial health · 2025

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

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

Who owns LUNDEBY GARTNERI AS?

KJERSTI KAMILLA RIISER GRYDELAND
LUNDEBY GARTNERI AS
NOK 5.7m rev. · NOK 2,000 profit

LUNDEBY GARTNERI AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDEBY GARTNERI AS

Who owns LUNDEBY GARTNERI AS?

KJERSTI KAMILLA RIISER GRYDELAND is the largest registered owner, with 33.3%.

What is the revenue of LUNDEBY GARTNERI AS?

LUNDEBY GARTNERI AS had revenue of NOK 5.7m in 2025.

Who is the general manager of LUNDEBY GARTNERI AS?

Kjersti Kamilla Riiser Grydeland is registered as general manager of LUNDEBY GARTNERI AS.

Where is LUNDEBY GARTNERI AS based?

LUNDEBY GARTNERI AS has its business address in Råde.

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.