BIZTRAC BETA
Business and other management consultancy activities

PEAK ACCOUNTING ADVISORY AS

Org. no. 934266412 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −130,000
Equity NOK −76,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−76k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−130k kr).

PEAK ACCOUNTING ADVISORY AS is registered as a limited company in Oslo, Oslo with organisation number 934266412. 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: “Utleie av personell og konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −130,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −130,000
Equity
NOK −76,000

Financial health · 2024

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

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

Who owns PEAK ACCOUNTING ADVISORY AS?

YOUSSRA MAAZIA
PEAK ACCOUNTING ADVISORY AS
NOK 0 rev. · NOK −130,000 profit

PEAK ACCOUNTING ADVISORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEAK ACCOUNTING ADVISORY AS

Who owns PEAK ACCOUNTING ADVISORY AS?

YOUSSRA MAAZIA is the largest registered owner, with 100.0%.

What is the revenue of PEAK ACCOUNTING ADVISORY AS?

PEAK ACCOUNTING ADVISORY AS had revenue of NOK 0 in 2024.

Where is PEAK ACCOUNTING ADVISORY AS based?

PEAK ACCOUNTING ADVISORY AS has its business address in Oslo.

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.