BIZTRAC BETA
Rental and operating of own or leased real estate

HAGNES EIENDOM AS

Org. no. 940176492 Limited company (AS) Levanger Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73,000
Equity NOK 1.0m
Incorporated 1986
Share capital NOK 34,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−73k kr).

HAGNES EIENDOM AS is registered as a limited company in Levanger, Trøndelag with organisation number 940176492. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 34,000, divided into 17 shares. The company's stated purpose is: “Utleievirksomhet av fast eiendom, transport av fyringsolje, samt alt som står i forbindelse med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73,000
Equity
NOK 1.0m
Est. value
NOK 949,000

Financial health · 2025

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

Who owns HAGNES EIENDOM AS?

LIV SYNNØVE HAGNES
HAGNES EIENDOM AS
NOK 0 rev. · NOK −73,000 profit

HAGNES EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAGNES EIENDOM AS own?

HAGNES EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HAGNES EIENDOM AS

Who owns HAGNES EIENDOM AS?

LIV SYNNØVE HAGNES is the largest registered owner, with 100.0%.

What is the revenue of HAGNES EIENDOM AS?

HAGNES EIENDOM AS had revenue of NOK 0 in 2025.

Where is HAGNES EIENDOM AS based?

HAGNES EIENDOM AS has its business address in Åsen.

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.