BIZTRAC BETA
Computer consultancy and computer facilities management activities

CORESOFT AS

Org. no. 932762447 Limited company (AS) Øygarden Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK −189,000
Equity NOK 187,000
Incorporated 2023
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−189k kr).

CORESOFT AS is registered as a limited company in Øygarden, Vestland with organisation number 932762447. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 400,000, divided into 400000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT og annet som naturlig sammenfaller med dette samt deltagelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK −189,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK −189,000
Equity
NOK 187,000
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns CORESOFT AS?

AZZLACK AS
CORESOFT AS
NOK 3.7m rev. · NOK −189,000 profit

CORESOFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CORESOFT AS

Who owns CORESOFT AS?

AZZLACK AS is the largest registered owner, with 70.0%.

What is the revenue of CORESOFT AS?

CORESOFT AS had revenue of NOK 3.7m in 2024.

Who is the general manager of CORESOFT AS?

Ove Andersen is registered as general manager of CORESOFT AS.

Where is CORESOFT AS based?

CORESOFT AS has its business address in Straume.

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.