BIZTRAC BETA
Buying and selling of own real estate

PILESTREDET 35 HOLDING AS

Org. no. 921892926 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −337,000
Equity NOK 447.3m
Incorporated 2018
Share capital NOK 5.5m

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−337k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-18 Avregistrert registrert 2026-06-18.

PILESTREDET 35 HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 921892926. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 5.5m, divided into 5452371 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −337,000
Equity
NOK 447.3m
Est. value
NOK 408.2m

Financial health · 2024

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

Who owns PILESTREDET 35 HOLDING AS?

MALLING CORE PLUS II HOLDING AS
PILESTREDET 35 HOLDING AS
· NOK −337,000 profit

PILESTREDET 35 HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PILESTREDET 35 HOLDING AS own?

PILESTREDET 35 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PILESTREDET 35 HOLDING AS

Who owns PILESTREDET 35 HOLDING AS?

MALLING CORE PLUS II HOLDING AS is the largest registered owner, with 61.6%.

Where is PILESTREDET 35 HOLDING AS based?

PILESTREDET 35 HOLDING 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.