biztrac. BETA
COMPANY REGISTER PROFILE
931477463 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HAHO22 AS

Org. no. 931477463 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 752,000
Operating profit NOK −7.4m
Equity NOK −11.0m
Incorporated 2023
Share capital NOK 877,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7,4 mill kr).

HAHO22 AS is registered as a limited company in Bergen, Vestland with organisation number 931477463. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 877,000, divided into 32000 shares. The company's stated purpose is: “Eie og forvalte aksje- og eiendomsinvesteringer og det som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 752,000 in revenue and NOK −7.4m in operating profit.

Key figures · 2025

Revenue
NOK 752,000
▼ −33 %
Operating profit
NOK −7.4m
▲ +15 %
Equity
NOK −11.0m
▼ −141 %

Financial health · 2025

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

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

Who owns HAHO22 AS?

HAHO22 AS
NOK 752,000 rev. · NOK −7.4m profit

HAHO22 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAHO22 AS

Who owns HAHO22 AS?

FREMRE EIENDOM AS is the largest registered owner, with 97.5%.

What is the revenue of HAHO22 AS?

HAHO22 AS had revenue of NOK 752,000 in 2025.

Where is HAHO22 AS based?

HAHO22 AS has its business address in Bergen.

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.