BIZTRAC BETA
Rental and operating of own or leased real estate

P&A HOLDING AS

Org. no. 997238893 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −1.4m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).

P&A HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997238893. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Erverve, eie, forvalte og omsette aksjer og selskapsandeler i andre virksomheter, samt det som måtte stå i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −1.4m

Financial health · 2024

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

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

Who owns P&A HOLDING AS?

Anders Estenstad
P&A HOLDING AS
NOK 0 rev. · NOK 0 profit

P&A HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does P&A HOLDING AS own?

P&A HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about P&A HOLDING AS

Who owns P&A HOLDING AS?

Anders Estenstad is the largest registered owner, with 98.0%.

What is the revenue of P&A HOLDING AS?

P&A HOLDING AS had revenue of NOK 0 in 2024.

Where is P&A HOLDING AS based?

P&A HOLDING AS has its business address in Trondheim.

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.