BIZTRAC BETA
Growing of other non-perennial crops

EGGEN GARTNERI AS

Org. no. 923427155 Limited company (AS) Indre Østfold Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 235,000
Equity NOK 1.3m
Incorporated 2019
Share capital NOK 30,000

EGGEN GARTNERI AS is registered as a limited company in Indre Østfold, Østfold with organisation number 923427155. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive gartnerivirksomhet med produksjon, kjøp og salg av egnede vekster og relaterte produkter i veksthus og friland. Snørydding og annen maskinell drift. Selskapet kan også delta i andre selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 235,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 235,000
Equity
NOK 1.3m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns EGGEN GARTNERI AS?

KJETIL EGGEN-DISKERUD
EGGEN GARTNERI AS
NOK 3.4m rev. · NOK 235,000 profit

EGGEN GARTNERI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EGGEN GARTNERI AS

Who owns EGGEN GARTNERI AS?

KJETIL EGGEN-DISKERUD is the largest registered owner, with 50.0%.

What is the revenue of EGGEN GARTNERI AS?

EGGEN GARTNERI AS had revenue of NOK 3.4m in 2025.

Who is the general manager of EGGEN GARTNERI AS?

Agnete Eggen-Diskerud is registered as general manager of EGGEN GARTNERI AS.

Where is EGGEN GARTNERI AS based?

EGGEN GARTNERI AS has its business address in Mysen.

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.