biztrac. BETA
COMPANY REGISTER PROFILE
935435552 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

HARBITZKVARTALENE UTVIKLING AS

Org. no. 935435552 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −146,000
Equity NOK −121,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HARBITZKVARTALENE UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 935435552. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Prosjektering og utvikling av fast eiendom samt alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −146,000
Equity
NOK −121,000

Financial health · 2025

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

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

Who owns HARBITZKVARTALENE UTVIKLING AS?

HARBITZKVARTALENE UTVIKLING AS
· NOK −146,000 profit

HARBITZKVARTALENE UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HARBITZKVARTALENE UTVIKLING AS

Who owns HARBITZKVARTALENE UTVIKLING AS?

BANE NOR EIENDOM AS is the largest registered owner, with 50.0%.

Who is the general manager of HARBITZKVARTALENE UTVIKLING AS?

Emil Paaske is registered as general manager of HARBITZKVARTALENE UTVIKLING AS.

Where is HARBITZKVARTALENE UTVIKLING AS based?

HARBITZKVARTALENE UTVIKLING 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.