BIZTRAC BETA
Rental and operating of own or leased real estate

HAGLES EIENDOMMER AS

Org. no. 932024756 Limited company (AS) Fredrikstad Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 3.1m
Equity NOK 14.3m
Incorporated 1982
Share capital NOK 600,000

HAGLES EIENDOMMER AS is registered as a limited company in Fredrikstad, Østfold with organisation number 932024756. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 600,000, divided into 300 shares. The company's stated purpose is: “Kjøpe, selge og eie eiendommer og alt som står i forbindelse hermed, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 3.1m
Equity
NOK 14.3m
Est. value
NOK 17.3m

Financial health · 2024

Liquidity
7.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
91.2%
Very good
Equity as a share of total capital

Who owns HAGLES EIENDOMMER AS?

DAVID ALEXANDER AVANN HAGLE
HAGLES EIENDOMMER AS
NOK 4.7m rev. · NOK 3.1m profit

HAGLES EIENDOMMER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAGLES EIENDOMMER AS

Who owns HAGLES EIENDOMMER AS?

DAVID ALEXANDER AVANN HAGLE is the largest registered owner, with 33.0%.

What is the revenue of HAGLES EIENDOMMER AS?

HAGLES EIENDOMMER AS had revenue of NOK 4.7m in 2025.

Who is the general manager of HAGLES EIENDOMMER AS?

Olav Alexander Avann Hagle is registered as general manager of HAGLES EIENDOMMER AS.

Where is HAGLES EIENDOMMER AS based?

HAGLES EIENDOMMER AS has its business address in Manstad.

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.