BIZTRAC BETA
Activities of employment placement agencies

NESTOR NORGE AS

Org. no. 928538729 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 14.6m
Operating profit NOK 511,000
Equity NOK 595,000
Incorporated 2021
Employees 10
Share capital NOK 500,000

NESTOR NORGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928538729. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 2021 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drive bemanningsvirksomhet, rekruttering, konsulenttjenester, rådgivning og annen virksomhet som naturlig står i forbindelse med dette, samt investeringer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.6m in revenue and NOK 511,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.6m
Operating profit
NOK 511,000
Equity
NOK 595,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns NESTOR NORGE AS?

BERGSTEN AS
NESTOR NORGE AS
NOK 14.6m rev. · NOK 511,000 profit

NESTOR NORGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NESTOR NORGE AS

Who owns NESTOR NORGE AS?

BERGSTEN AS is the largest registered owner, with 60.0%.

What is the revenue of NESTOR NORGE AS?

NESTOR NORGE AS had revenue of NOK 14.6m in 2025.

Who is the general manager of NESTOR NORGE AS?

Rune Jakobsen is registered as general manager of NESTOR NORGE AS.

Where is NESTOR NORGE AS based?

NESTOR NORGE 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.