BIZTRAC BETA
Wholesale of fruit and vegetables

INNLANDET GRØNT AS

Org. no. 919444118 Limited company (AS) Østre Toten Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 15.7m
Operating profit NOK 13,000
Equity NOK 1.4m
Incorporated 2017
Share capital NOK 201,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

INNLANDET GRØNT AS is registered as a limited company in Østre Toten, Innlandet with organisation number 919444118. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 2017. Registered share capital is NOK 201,000, divided into 201 shares. The company's stated purpose is: “Kjøp og salg av grønnsaker, og andre aktiviteter forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.7m in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.7m
Operating profit
NOK 13,000
Equity
NOK 1.4m
Est. value
NOK 738,000

Financial health · 2024

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.3%
Good
Equity as a share of total capital

Who owns INNLANDET GRØNT AS?

CACTUS INVEST AS
INNLANDET GRØNT AS
NOK 15.7m rev. · NOK 13,000 profit

INNLANDET GRØNT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNLANDET GRØNT AS

Who owns INNLANDET GRØNT AS?

CACTUS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of INNLANDET GRØNT AS?

INNLANDET GRØNT AS had revenue of NOK 15.7m in 2024.

Who is the general manager of INNLANDET GRØNT AS?

Anna Ostrowska-Socha is registered as general manager of INNLANDET GRØNT AS.

Where is INNLANDET GRØNT AS based?

INNLANDET GRØNT AS has its business address in Lena.

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.