biztrac. BETA
COMPANY REGISTER PROFILE
995849615 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

P&G HOLDING AS

Org. no. 995849615 Limited company (AS) Bærum Incorporated 2010 Active
Revenue 2025 NOK 737,000
Operating profit NOK −9,000
Equity NOK 862,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

P&G HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 995849615. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre eierskap og investere i selskaper, eiendom og eventuelle andre finansielle objekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 737,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 737,000
▼ −14 %
Operating profit
NOK −9,000
▼ −107 %
Equity
NOK 862,000
▼ −23 %
Est. value
NOK 701,000

Financial health · 2025

Liquidity
0.59
Weak
Current assets ÷ current liabilities
Profitability
-0.4%
Not satisfactory
Return on total assets
Solidity
61.2%
Very good
Equity as a share of total capital

Who owns P&G HOLDING AS?

P&G HOLDING AS
NOK 737,000 rev. · NOK −9,000 profit

P&G HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does P&G HOLDING AS own?

P&G HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about P&G HOLDING AS

Who owns P&G HOLDING AS?

STOPLIGHT AS is the largest registered owner, with 100.0%.

What is the revenue of P&G HOLDING AS?

P&G HOLDING AS had revenue of NOK 737,000 in 2025.

Where is P&G HOLDING AS based?

P&G HOLDING AS has its business address in Jar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.