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

HA10E MFL AS

Org. no. 926038753 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 18.9m
Operating profit NOK 824,000
Equity NOK 530,000
Incorporated 2020
Share capital NOK 30,000

HA10E MFL AS is registered as a limited company in Oslo, Oslo with organisation number 926038753. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i eiendom/aksjer, eie, drifte og utvikle eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.9m in revenue and NOK 824,000 in operating profit.

Former names: HAL 12 D AS, HARBITZPARKEN AS

Key figures · 2025

Revenue
NOK 18.9m
▲ +9186 %
Operating profit
NOK 824,000
▲ +413 %
Equity
NOK 530,000
▲ +314 %
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
8.88
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
1.9%
Not satisfactory
Equity as a share of total capital

Who owns HA10E MFL AS?

HA10E MFL AS
NOK 18.9m rev. · NOK 824,000 profit

HA10E MFL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HA10E MFL AS

Who owns HA10E MFL AS?

HARBITZ EIENDOM II AS is the largest registered owner, with 50.0%.

What is the revenue of HA10E MFL AS?

HA10E MFL AS had revenue of NOK 18.9m in 2025.

Who is the general manager of HA10E MFL AS?

Emil Paaske is registered as general manager of HA10E MFL AS.

Where is HA10E MFL AS based?

HA10E MFL 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.