BIZTRAC BETA
Activities of employment placement agencies

HEADVISOR AS

Org. no. 985395993 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 43.4m
Operating profit NOK 700,000
Equity NOK 2.6m
Incorporated 2003
Share capital NOK 120,000

HEADVISOR AS is registered as a limited company in Bergen, Vestland with organisation number 985395993. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2003. Registered share capital is NOK 120,000, divided into 1200 shares. The company's stated purpose is: “Rådgivning innen rekruttering og organisasjons/medarbeiderutvikling og alt som har sammenheng med dette, inklusiv å delta i selskaper og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.4m in revenue and NOK 700,000 in operating profit.

Key figures · 2024

Revenue
NOK 43.4m
Operating profit
NOK 700,000
Equity
NOK 2.6m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns HEADVISOR AS?

MGA CONSULTING AS
HEADVISOR AS
NOK 43.4m rev. · NOK 700,000 profit

HEADVISOR AS has 8 registered shareholders:

All shareholders and roles →

Which companies does HEADVISOR AS own?

HEADVISOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEADVISOR AS

Who owns HEADVISOR AS?

MGA CONSULTING AS is the largest registered owner, with 25.0%.

What is the revenue of HEADVISOR AS?

HEADVISOR AS had revenue of NOK 43.4m in 2024.

Who is the general manager of HEADVISOR AS?

Lars Jakob Arnøy is registered as general manager of HEADVISOR AS.

Where is HEADVISOR AS based?

HEADVISOR AS has its business address in Bergen.

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.