BIZTRAC BETA
Rental and operating of own or leased real estate

ENGER UTVIKLING AS

Org. no. 991342168 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 5.7m
Equity NOK 59.8m
Incorporated 2007
Share capital NOK 60.0m

Signals

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

ENGER UTVIKLING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 991342168. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 60.0m, divided into 60000 shares. The company's stated purpose is: “Erverv, planlegging og prosjektering, utbygging og drift av eiendom og bygg. Videre har selskapet til formål å organisere eller delta i tiltak eller selskap som har sammenheng med ovennevnte formål”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 5.7m in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 5.7m
Equity
NOK 59.8m
Est. value
NOK 50.6m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns ENGER UTVIKLING AS?

NHP SØR AS
ENGER UTVIKLING AS
NOK 8.7m rev. · NOK 5.7m profit

ENGER UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGER UTVIKLING AS

Who owns ENGER UTVIKLING AS?

NHP SØR AS is the largest registered owner, with 100.0%.

What is the revenue of ENGER UTVIKLING AS?

ENGER UTVIKLING AS had revenue of NOK 8.7m in 2025.

Where is ENGER UTVIKLING AS based?

ENGER UTVIKLING 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.