BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

VIKAR I NORGE AS

Org. no. 996520153 Limited company (AS) Nordreisa Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 411,000
Equity NOK 1.9m
Incorporated 2011
Employees 15
Share capital NOK 100,000

VIKAR I NORGE AS is registered as a limited company in Nordreisa, Troms with organisation number 996520153. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2011 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av arbeidskraft spesielt rettet mot helsevesenet og det som naturlig følger av dette, herunder deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 411,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 411,000
Equity
NOK 1.9m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns VIKAR I NORGE AS?

AM DIRECT AS
VIKAR I NORGE AS
NOK 5.6m rev. · NOK 411,000 profit

VIKAR I NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKAR I NORGE AS

Who owns VIKAR I NORGE AS?

AM DIRECT AS is the largest registered owner, with 100.0%.

What is the revenue of VIKAR I NORGE AS?

VIKAR I NORGE AS had revenue of NOK 5.6m in 2024.

Who is the general manager of VIKAR I NORGE AS?

Bjørn Magne Amundsgård is registered as general manager of VIKAR I NORGE AS.

Where is VIKAR I NORGE AS based?

VIKAR I NORGE AS has its business address in Storslett.

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.