BIZTRAC BETA
Manufacture of other food products n.e.c.

NORINSECT AUREOSEN AS

Org. no. 935738393 Limited company (AS) Hustadvika Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-10 Aksjekapital registrert 2026-06-10.

NORINSECT AUREOSEN AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 935738393. The business is classified under manufacture of other food products n.e.c. (NACE 10.890). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Opdrett av melorm og produksjon av melormprodukter til bruk i mat, fôr og gjødsel, samt det som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 20,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns NORINSECT AUREOSEN AS?

NORINSECT HOLDING AS
NORINSECT AUREOSEN AS
· NOK −3,000 profit

NORINSECT AUREOSEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NORINSECT AUREOSEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about NORINSECT AUREOSEN AS

Who owns NORINSECT AUREOSEN AS?

NORINSECT HOLDING AS is the largest registered owner, with 100.0%.

Where is NORINSECT AUREOSEN AS based?

NORINSECT AUREOSEN AS has its business address in Aureosen.

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.