BIZTRAC BETA
Computer consultancy and computer facilities management activities

KVELLO HANSEN KOMPETANSE AS

Org. no. 915577814 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 322,000
Equity NOK 1.5m
Incorporated 2015
Share capital NOK 30,000

KVELLO HANSEN KOMPETANSE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915577814. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av konsulent tjenester innen IT.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 322,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 322,000
Equity
NOK 1.5m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns KVELLO HANSEN KOMPETANSE AS?

BJØRNAR KVELLO HANSEN
KVELLO HANSEN KOMPETANSE AS
NOK 3.0m rev. · NOK 322,000 profit

KVELLO HANSEN KOMPETANSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVELLO HANSEN KOMPETANSE AS

Who owns KVELLO HANSEN KOMPETANSE AS?

BJØRNAR KVELLO HANSEN is the largest registered owner, with 100.0%.

What is the revenue of KVELLO HANSEN KOMPETANSE AS?

KVELLO HANSEN KOMPETANSE AS had revenue of NOK 3.0m in 2024.

Who is the general manager of KVELLO HANSEN KOMPETANSE AS?

Bjørnar Kvello Hansen is registered as general manager of KVELLO HANSEN KOMPETANSE AS.

Where is KVELLO HANSEN KOMPETANSE AS based?

KVELLO HANSEN KOMPETANSE 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.