BIZTRAC BETA
Uoppgitt

PETTERSPLASSEN HOLDING AS

Org. no. 927511495 Limited company (AS) Levanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 1.1m
Incorporated 2021
Share capital NOK 40,000

Signals

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

PETTERSPLASSEN HOLDING AS is registered as a limited company in Levanger, Trøndelag with organisation number 927511495. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper uansett formål, samt forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 1.1m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns PETTERSPLASSEN HOLDING AS?

HANS PETTER SUNDAL
PETTERSPLASSEN HOLDING AS
NOK 0 rev. · NOK −13,000 profit

PETTERSPLASSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PETTERSPLASSEN HOLDING AS own?

PETTERSPLASSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PETTERSPLASSEN HOLDING AS

Who owns PETTERSPLASSEN HOLDING AS?

HANS PETTER SUNDAL is the largest registered owner, with 100.0%.

What is the revenue of PETTERSPLASSEN HOLDING AS?

PETTERSPLASSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is PETTERSPLASSEN HOLDING AS based?

PETTERSPLASSEN HOLDING AS has its business address in Levanger.

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.