BIZTRAC BETA
Wholesale of information and communication equipment

AZOLVER NORGE AS

Org. no. 982156203 Limited company (AS) Lørenskog Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 88.5m
Operating profit NOK 5.3m
Equity NOK 21.4m
Incorporated 2000
Employees 14
Share capital NOK 14.9m

AZOLVER NORGE AS is registered as a limited company in Lørenskog, Akershus with organisation number 982156203. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2000 and has 14 registered employees. Registered share capital is NOK 14.9m, divided into 2810000 shares. The company's stated purpose is: “Å forestå, selge, kjøpe og vedlikeholde kontorutstyr og annen virksomhet beslektet med denne, inkludert deltakelse i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 88.5m in revenue and NOK 5.3m in operating profit.

Key figures · 2024

Revenue
NOK 88.5m
Operating profit
NOK 5.3m
Equity
NOK 21.4m
Est. value
NOK 33.2m

Financial health · 2024

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

Who owns AZOLVER NORGE AS?

FRANCOTYPPOSTALIA HOLDING AG
AZOLVER NORGE AS
NOK 88.5m rev. · NOK 5.3m profit

AZOLVER NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AZOLVER NORGE AS

Who owns AZOLVER NORGE AS?

FRANCOTYPPOSTALIA HOLDING AG is the largest registered owner, with 100.0%.

What is the revenue of AZOLVER NORGE AS?

AZOLVER NORGE AS had revenue of NOK 88.5m in 2024.

Who is the general manager of AZOLVER NORGE AS?

Knut Rostad is registered as general manager of AZOLVER NORGE AS.

Where is AZOLVER NORGE AS based?

AZOLVER NORGE AS has its business address in Lørenskog.

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.