biztrac. BETA
COMPANY REGISTER PROFILE
912673014 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other information technology and computer service activities

VEEAM SOFTWARE NORWAY AS

Org. no. 912673014 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 15.0m
Operating profit NOK 698,000
Equity NOK 4.6m
Incorporated 2013
Share capital NOK 30,000

VEEAM SOFTWARE NORWAY AS is registered as a limited company in Oslo, Oslo with organisation number 912673014. The business is classified under other information technology and computer service activities (NACE 62.900). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie og drive andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.0m in revenue and NOK 698,000 in operating profit.

Former names: SIVOW 22 AS

Key figures · 2025

Revenue
NOK 15.0m
▲ +7 %
Operating profit
NOK 698,000
▲ +4 %
Equity
NOK 4.6m
▲ +11 %
Est. value
NOK 6.2m

Financial health · 2025

Liquidity
1.94
Good
Current assets ÷ current liabilities
Profitability
8.5%
Satisfactory
Return on total assets
Solidity
48.5%
Very good
Equity as a share of total capital

Who owns VEEAM SOFTWARE NORWAY AS?

VEEAM SOFTWARE GROUP GMBH CH
VEEAM SOFTWARE NORWAY AS
NOK 15.0m rev. · NOK 698,000 profit

VEEAM SOFTWARE NORWAY AS has 1 registered shareholder:

  • VEEAM SOFTWARE GROUP GMBH 100.0%
All shareholders and roles →

Frequently asked questions about VEEAM SOFTWARE NORWAY AS

Who owns VEEAM SOFTWARE NORWAY AS?

VEEAM SOFTWARE GROUP GMBH is the largest registered owner, with 100.0%.

What is the revenue of VEEAM SOFTWARE NORWAY AS?

VEEAM SOFTWARE NORWAY AS had revenue of NOK 15.0m in 2025.

Where is VEEAM SOFTWARE NORWAY AS based?

VEEAM SOFTWARE NORWAY 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 03.10.2026.

Report a problem

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