BIZTRAC BETA
Computer consultancy and computer facilities management activities

Q-FREE NORGE AS

Org. no. 920771793 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 383.8m
Operating profit NOK −76.6m
Equity NOK 107.1m
Incorporated 2018
Employees 103
Share capital NOK 15.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76,6 mill kr).

Q-FREE NORGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 920771793. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018 and has 103 registered employees. Registered share capital is NOK 15.8m, divided into 1000 shares. The company's stated purpose is: “Selv og/eller gjennom eierskap i andre selskaper, å drive forskning, utvikling, produksjon, drift og salg av informasjonsteknologi produkter og systemer samt alt som herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 383.8m in revenue and NOK −76.6m in operating profit.

Key figures · 2024

Revenue
NOK 383.8m
Operating profit
NOK −76.6m
Equity
NOK 107.1m
Est. value
NOK 689.9m

Financial health · 2024

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns Q-FREE NORGE AS?

Q-FREE AS
Q-FREE NORGE AS
NOK 383.8m rev. · NOK −76.6m profit

Q-FREE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Q-FREE NORGE AS

Who owns Q-FREE NORGE AS?

Q-FREE AS is the largest registered owner, with 100.0%.

What is the revenue of Q-FREE NORGE AS?

Q-FREE NORGE AS had revenue of NOK 383.8m in 2024.

Where is Q-FREE NORGE AS based?

Q-FREE NORGE AS has its business address in Ranheim.

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.