BIZTRAC BETA
Rental and operating of own or leased real estate

HALLSET HAGE AS

Org. no. 997480112 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 3.1m
Equity NOK 2.1m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HALLSET HAGE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 997480112. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging, drift og utleie av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovenfornevnte formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 3.1m
Equity
NOK 2.1m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns HALLSET HAGE AS?

NHP EIENDOM AS
HALLSET HAGE AS
NOK 4.7m rev. · NOK 3.1m profit

HALLSET HAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALLSET HAGE AS

Who owns HALLSET HAGE AS?

NHP EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HALLSET HAGE AS?

HALLSET HAGE AS had revenue of NOK 4.7m in 2024.

Where is HALLSET HAGE AS based?

HALLSET HAGE AS has its business address in Trondheim.

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.