BIZTRAC BETA
COMPANY REGISTER PROFILE
919788232 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

PIPPI AS

Org. no. 919788232 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK −46,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−46k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

PIPPI AS is registered as a limited company in Oslo, Oslo with organisation number 919788232. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, selskaper, og investeringer ellers.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK −46,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns PIPPI AS?

MØLLESVINGEN 2 AS
PIPPI AS
NOK 0 rev. · NOK −8,000 profit

PIPPI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIPPI AS

Who owns PIPPI AS?

MØLLESVINGEN 2 AS is the largest registered owner, with 100.0%.

What is the revenue of PIPPI AS?

PIPPI AS had revenue of NOK 0 in 2025.

Who is the general manager of PIPPI AS?

Amy Ingrid Secher is registered as general manager of PIPPI AS.

Where is PIPPI AS based?

PIPPI 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.