BIZTRAC BETA
Activities of employment placement agencies

ENKEL BEMANNING NORD AS

Org. no. 934385020 Limited company (AS) Vadsø Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.1m
Equity NOK 125,000
Incorporated 2024
Employees 36
Share capital NOK 40,000

ENKEL BEMANNING NORD AS is registered as a limited company in Vadsø, Finnmark with organisation number 934385020. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2024 and has 36 registered employees. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Utleie- og bemmanningsformidling av personell innen helse- og omsorgstjenester og barnevernstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.1m
Equity
NOK 125,000
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.2%
Weak
Equity as a share of total capital

Who owns ENKEL BEMANNING NORD AS?

MUNKERUD HOLDING AS
ENKEL BEMANNING NORD AS
NOK 1.9m rev. · NOK 1.1m profit

ENKEL BEMANNING NORD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENKEL BEMANNING NORD AS

Who owns ENKEL BEMANNING NORD AS?

MUNKERUD HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of ENKEL BEMANNING NORD AS?

ENKEL BEMANNING NORD AS had revenue of NOK 1.9m in 2024.

Who is the general manager of ENKEL BEMANNING NORD AS?

Runar Berg Pedersen is registered as general manager of ENKEL BEMANNING NORD AS.

Where is ENKEL BEMANNING NORD AS based?

ENKEL BEMANNING NORD AS has its business address in Vadsø.

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.