BIZTRAC BETA
Manufacture of fruit and vegetable juice

INDERØY MOSTERI AS

Org. no. 922606390 Limited company (AS) Inderøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 833,000
Equity NOK 781,000
Incorporated 2019
Employees 8
Share capital NOK 30,000

INDERØY MOSTERI AS is registered as a limited company in Inderøy, Trøndelag with organisation number 922606390. The business is classified under manufacture of fruit and vegetable juice (NACE 10.320). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Tilby mottak, pressing, foredling og salg av frukt, bær, grønnsaker og ville vekster, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 833,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 833,000
Equity
NOK 781,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns INDERØY MOSTERI AS?

MAREN BREKKVASSMO MYRVOLD
INDERØY MOSTERI AS
NOK 5.6m rev. · NOK 833,000 profit

INDERØY MOSTERI AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INDERØY MOSTERI AS

Who owns INDERØY MOSTERI AS?

MAREN BREKKVASSMO MYRVOLD is the largest registered owner, with 45.0%.

What is the revenue of INDERØY MOSTERI AS?

INDERØY MOSTERI AS had revenue of NOK 5.6m in 2024.

Who is the general manager of INDERØY MOSTERI AS?

Yngve Henriksen is registered as general manager of INDERØY MOSTERI AS.

Where is INDERØY MOSTERI AS based?

INDERØY MOSTERI AS has its business address in Inderøy.

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.