biztrac. BETA
COMPANY REGISTER PROFILE
933387437 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

CONMUTO AS

Org. no. 933387437 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 1.3m
Equity NOK 759,000
Incorporated 2024
Share capital NOK 100,000

CONMUTO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933387437. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentselskap innen IT og endringsledelse. Utvikling av applikasjoner, software og migrering av data. Lager både skreddersydde og standard integrasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
▲ +64 %
Operating profit
NOK 1.3m
▲ +29 %
Equity
NOK 759,000
▼ −15 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
68.1%
Very good
Return on total assets
Solidity
29.6%
Good
Equity as a share of total capital

Who owns CONMUTO AS?

CONMUTO AS
NOK 3.1m rev. · NOK 1.3m profit

CONMUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CONMUTO AS

Who owns CONMUTO AS?

EDB DESIGN AS is the largest registered owner, with 100.0%.

What is the revenue of CONMUTO AS?

CONMUTO AS had revenue of NOK 3.1m in 2025.

Who is the general manager of CONMUTO AS?

Jon Vidar Eidsaa is registered as general manager of CONMUTO AS.

Where is CONMUTO AS based?

CONMUTO AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.