BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

NH BEMANNING AS

Org. no. 918931406 Limited company (AS) Ullensaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 50.9m
Operating profit NOK −3.4m
Equity NOK 1.6m
Incorporated 2017
Employees 27
Share capital NOK 30,000

Signals

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

NH BEMANNING AS is registered as a limited company in Ullensaker, Akershus with organisation number 918931406. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2017 and has 27 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utleie av mannskap, bemmanningsbyrå.”. The most recent filed accounts, for the 2024 financial year, show NOK 50.9m in revenue and NOK −3.4m in operating profit.

Key figures · 2024

Revenue
NOK 50.9m
Operating profit
NOK −3.4m
Equity
NOK 1.6m
Est. value
NOK 31.7m

Financial health · 2024

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

Who owns NH BEMANNING AS?

JESK HOLDING APS
NH BEMANNING AS
NOK 50.9m rev. · NOK −3.4m profit

NH BEMANNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NH BEMANNING AS

Who owns NH BEMANNING AS?

JESK HOLDING APS is the largest registered owner, with 100.0%.

What is the revenue of NH BEMANNING AS?

NH BEMANNING AS had revenue of NOK 50.9m in 2024.

Who is the general manager of NH BEMANNING AS?

Jan Erik Knudsgaard Skou is registered as general manager of NH BEMANNING AS.

Where is NH BEMANNING AS based?

NH BEMANNING AS has its business address in Jessheim.

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.