BIZTRAC BETA
Computer consultancy and computer facilities management activities

KEYPRO AS

Org. no. 990051232 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 21.9m
Operating profit NOK 11.7m
Equity NOK 502,000
Incorporated 2006
Employees 9
Share capital NOK 100,000

Signals

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

KEYPRO AS is registered as a limited company in Oslo, Oslo with organisation number 990051232. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2006 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulent- og salgsvirksomhet innen IT og GIS samt utvikling av programvare for GIS.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.9m in revenue and NOK 11.7m in operating profit.

Key figures · 2024

Revenue
NOK 21.9m
Operating profit
NOK 11.7m
Equity
NOK 502,000
Est. value
NOK 37.8m

Financial health · 2024

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

Who owns KEYPRO AS?

GEOMATIKK HOLDING AS
KEYPRO AS
NOK 21.9m rev. · NOK 11.7m profit

KEYPRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEYPRO AS

Who owns KEYPRO AS?

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

What is the revenue of KEYPRO AS?

KEYPRO AS had revenue of NOK 21.9m in 2024.

Who is the general manager of KEYPRO AS?

Jesper Mølgaard is registered as general manager of KEYPRO AS.

Where is KEYPRO AS based?

KEYPRO AS has its business address in Oslo.

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.