BIZTRAC BETA
Growing of vegetables and melons, roots and tubers

INDERØY SOPP AS

Org. no. 914262437 Limited company (AS) Inderøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 45,000
Operating profit NOK −897
Equity NOK −120,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−120k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−897 kr).

INDERØY SOPP AS is registered as a limited company in Inderøy, Trøndelag with organisation number 914262437. The business is classified under growing of vegetables and melons, roots and tubers (NACE 01.130). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Virksomhet innen dyrking og salg av sopp.”. The most recent filed accounts, for the 2025 financial year, show NOK 45,000 in revenue and NOK −897 in operating profit.

Key figures · 2025

Revenue
NOK 45,000
Operating profit
NOK −897
Equity
NOK −120,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-842.6%
Weak
Equity as a share of total capital

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

Who owns INDERØY SOPP AS?

Dan Calin Pop
INDERØY SOPP AS
NOK 45,000 rev. · NOK −897 profit

INDERØY SOPP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDERØY SOPP AS

Who owns INDERØY SOPP AS?

Dan Calin Pop is the largest registered owner, with 100.0%.

What is the revenue of INDERØY SOPP AS?

INDERØY SOPP AS had revenue of NOK 45,000 in 2025.

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

Dan Calin Pop is registered as general manager of INDERØY SOPP AS.

Where is INDERØY SOPP AS based?

INDERØY SOPP 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.