BIZTRAC BETA
Organisation of conventions and trade shows

VOICE OF PEACE AS

Org. no. 931783645 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 4,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

VOICE OF PEACE AS is registered as a limited company in Oslo, Oslo with organisation number 931783645. The business is classified under organisation of conventions and trade shows (NACE 82.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning, foredrag, planlegging og gjennomføring av Int. fredsmøter, konferanser og seminarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 4,000
Est. value
NOK 6,000

Financial health · 2025

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

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

Who owns VOICE OF PEACE AS?

AAMIR JAVED SHEIKH
VOICE OF PEACE AS
NOK 0 rev. · NOK −4,000 profit

VOICE OF PEACE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOICE OF PEACE AS

Who owns VOICE OF PEACE AS?

AAMIR JAVED SHEIKH is the largest registered owner, with 100.0%.

What is the revenue of VOICE OF PEACE AS?

VOICE OF PEACE AS had revenue of NOK 0 in 2025.

Who is the general manager of VOICE OF PEACE AS?

Aamir Javed Sheikh is registered as general manager of VOICE OF PEACE AS.

Where is VOICE OF PEACE AS based?

VOICE OF PEACE 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.