BIZTRAC BETA
Business and other management consultancy activities

PEOPLESEARCH AS

Org. no. 833809342 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 491,000
Operating profit NOK 33,000
Equity NOK 76,000
Incorporated 2024
Share capital NOK 30,000

PEOPLESEARCH AS is registered as a limited company in Asker, Akershus with organisation number 833809342. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen bedriftsrådgivning, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 491,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 491,000
Operating profit
NOK 33,000
Equity
NOK 76,000
Est. value
NOK 204,000

Financial health · 2025

Liquidity
1.98
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
49.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PEOPLESEARCH AS?

KJETIL KVERNSTUEN
PEOPLESEARCH AS
NOK 491,000 rev. · NOK 33,000 profit

PEOPLESEARCH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEOPLESEARCH AS

Who owns PEOPLESEARCH AS?

KJETIL KVERNSTUEN is the largest registered owner, with 100.0%.

What is the revenue of PEOPLESEARCH AS?

PEOPLESEARCH AS had revenue of NOK 491,000 in 2025.

Who is the general manager of PEOPLESEARCH AS?

Kjetil Kvernstuen is registered as general manager of PEOPLESEARCH AS.

Where is PEOPLESEARCH AS based?

PEOPLESEARCH AS has its business address in Åros.

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.