BIZTRAC BETA
Business and other management consultancy activities

PEAK1 ADVISORS AS

Org. no. 923136304 Limited company (AS) Vestby Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK −133,000
Equity NOK 396,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−133k kr).

PEAK1 ADVISORS AS is registered as a limited company in Vestby, Akershus with organisation number 923136304. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Strategisk rådgivning, coaching, publisering av bøker, seminarer/foredrag, investeringer i eiendom og aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK −133,000 in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK −133,000
Equity
NOK 396,000
Est. value
NOK 353,000

Financial health · 2024

Liquidity
1.68
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
57.2%
Very good
Equity as a share of total capital

Who owns PEAK1 ADVISORS AS?

PETTER KLEPPE
PEAK1 ADVISORS AS
NOK 200,000 rev. · NOK −133,000 profit

PEAK1 ADVISORS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PEAK1 ADVISORS AS own?

PEAK1 ADVISORS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PEAK1 ADVISORS AS

Who owns PEAK1 ADVISORS AS?

PETTER KLEPPE is the largest registered owner, with 100.0%.

What is the revenue of PEAK1 ADVISORS AS?

PEAK1 ADVISORS AS had revenue of NOK 200,000 in 2024.

Where is PEAK1 ADVISORS AS based?

PEAK1 ADVISORS AS has its business address in Son.

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.