biztrac. BETA
COMPANY REGISTER PROFILE
997030508 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HARALDRUDVEIEN 31 AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

HARALDRUDVEIEN 31 AS

Org. no. 997030508 Limited company (AS) Oslo Incorporated 2011 In liquidation
Ownership graph ↗
Operating profit NOK −59,000
Equity NOK 17.6m
Incorporated 2011
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−59k kr).

HARALDRUDVEIEN 31 AS is registered as a limited company in Oslo, Oslo with organisation number 997030508. 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 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i, eie, drive, leie ut, utvikle og realisere fast eiendom, direkte eller indirekte gjennom deltakelse i andre selskaper, og alt som står i forbindelse med dette.”.

Former names: STARTFASE 461 AS

Key figures · 2025

Operating profit
NOK −59,000
▼ −1 %
Equity
NOK 17.6m
▲ +1314 %

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.8%
Not satisfactory
Equity as a share of total capital

Who owns HARALDRUDVEIEN 31 AS?

HARALDRUDVEIEN 31 AS
· NOK −59,000 profit

HARALDRUDVEIEN 31 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HARALDRUDVEIEN 31 AS

Who owns HARALDRUDVEIEN 31 AS?

OSLO PENSJONSFORSIKRING AS is the largest registered owner, with 100.0%.

Where is HARALDRUDVEIEN 31 AS based?

HARALDRUDVEIEN 31 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 03.10.2026.

Report a problem

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