BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

ROBUST BEMANNING AS

Org. no. 931123939 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 141.6m
Operating profit NOK 4.9m
Equity NOK 1.1m
Incorporated 2023
Employees 197
Share capital NOK 30,000

ROBUST BEMANNING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931123939. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2023 and has 197 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utleie av arbeidskraft samt virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 141.6m in revenue and NOK 4.9m in operating profit.

Key figures · 2025

Revenue
NOK 141.6m
Operating profit
NOK 4.9m
Equity
NOK 1.1m
Est. value
NOK 21.2m

Financial health · 2025

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

Who owns ROBUST BEMANNING AS?

ROBUST MANAGEMENT AS
ROBUST BEMANNING AS
NOK 141.6m rev. · NOK 4.9m profit

ROBUST BEMANNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROBUST BEMANNING AS

Who owns ROBUST BEMANNING AS?

ROBUST MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of ROBUST BEMANNING AS?

ROBUST BEMANNING AS had revenue of NOK 141.6m in 2025.

Who is the general manager of ROBUST BEMANNING AS?

Kristine Ødegaard is registered as general manager of ROBUST BEMANNING AS.

Where is ROBUST BEMANNING AS based?

ROBUST BEMANNING AS has its business address in Trondheim.

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.