BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

TOPTEMP ROMERIKE AS

Org. no. 987623489 Limited company (AS) Lillestrøm Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 48.0m
Operating profit NOK 5.0m
Equity NOK 3.3m
Incorporated 2004
Employees 72
Share capital NOK 100,000

TOPTEMP ROMERIKE AS is registered as a limited company in Lillestrøm, Akershus with organisation number 987623489. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2004 and has 72 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rekruttering og utleie av personell samt investering i relaterte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.0m in revenue and NOK 5.0m in operating profit.

Key figures · 2024

Revenue
NOK 48.0m
Operating profit
NOK 5.0m
Equity
NOK 3.3m
Est. value
NOK 22.6m

Financial health · 2024

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

Who owns TOPTEMP ROMERIKE AS?

TOPTEMP GROUP AS
TOPTEMP ROMERIKE AS
NOK 48.0m rev. · NOK 5.0m profit

TOPTEMP ROMERIKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPTEMP ROMERIKE AS

Who owns TOPTEMP ROMERIKE AS?

TOPTEMP GROUP AS is the largest registered owner, with 90.0%.

What is the revenue of TOPTEMP ROMERIKE AS?

TOPTEMP ROMERIKE AS had revenue of NOK 48.0m in 2024.

Who is the general manager of TOPTEMP ROMERIKE AS?

Nina Sennerud is registered as general manager of TOPTEMP ROMERIKE AS.

Where is TOPTEMP ROMERIKE AS based?

TOPTEMP ROMERIKE AS has its business address in Lillestrøm.

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.