BIZTRAC BETA
Computer programming activities

CORRON AS

Org. no. 919059362 Limited company (AS) Molde Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 47,000
Equity NOK 635,000
Incorporated 2017
Share capital NOK 60,000

Signals

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

CORRON AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 919059362. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Å utvikle, markedsføre, produsere og selge en komplett løsning for å kontrollere korrosjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 47,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 47,000
Equity
NOK 635,000
Est. value
NOK 463,000

Financial health · 2024

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

Who owns CORRON AS?

EFFEE AS
CORRON AS
NOK 1.3m rev. · NOK 47,000 profit

CORRON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CORRON AS own?

CORRON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CORRON AS

Who owns CORRON AS?

EFFEE AS is the largest registered owner, with 100.0%.

What is the revenue of CORRON AS?

CORRON AS had revenue of NOK 1.3m in 2024.

Who is the general manager of CORRON AS?

Stine Nordvik is registered as general manager of CORRON AS.

Where is CORRON AS based?

CORRON AS has its business address in Molde.

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.