BIZTRAC BETA
Computer consultancy and computer facilities management activities

DIGPRO NORGE AS

Org. no. 930260851 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 8.3m
Operating profit NOK 502,000
Equity NOK 1.1m
Incorporated 2022
Employees 5
Share capital NOK 30,000

DIGPRO NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 930260851. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive virksomhet knyttet til utvikling og handel med produkter og tjenester innen informasjonsteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.3m in revenue and NOK 502,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.3m
Operating profit
NOK 502,000
Equity
NOK 1.1m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns DIGPRO NORGE AS?

DIGPRO AB
DIGPRO NORGE AS
NOK 8.3m rev. · NOK 502,000 profit

DIGPRO NORGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DIGPRO NORGE AS er morselskap for 1 datterselskap:

Frequently asked questions about DIGPRO NORGE AS

Who owns DIGPRO NORGE AS?

DIGPRO AB is the largest registered owner, with 100.0%.

What is the revenue of DIGPRO NORGE AS?

DIGPRO NORGE AS had revenue of NOK 8.3m in 2025.

Who is the general manager of DIGPRO NORGE AS?

Frode Solaas Gundersen is registered as general manager of DIGPRO NORGE AS.

Where is DIGPRO NORGE AS based?

DIGPRO NORGE 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.