BIZTRAC BETA
Development of building projects

HØISETH UTVIKLING AS

Org. no. 992675365 Limited company (AS) Trondheim Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −99,000
Equity NOK −3.9m
Incorporated 2008
Share capital NOK 40,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,9 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−99k kr).

HØISETH UTVIKLING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 992675365. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2008. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −99,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −99,000
Equity
NOK −3.9m

Financial health · 2025

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-54.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HØISETH UTVIKLING AS?

LUND ØSTRE AS
HØISETH UTVIKLING AS
NOK 0 rev. · NOK −99,000 profit

HØISETH UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HØISETH UTVIKLING AS

Who owns HØISETH UTVIKLING AS?

LUND ØSTRE AS is the largest registered owner, with 75.0%.

What is the revenue of HØISETH UTVIKLING AS?

HØISETH UTVIKLING AS had revenue of NOK 0 in 2025.

Who is the general manager of HØISETH UTVIKLING AS?

Per Erik Austberg is registered as general manager of HØISETH UTVIKLING AS.

Where is HØISETH UTVIKLING AS based?

HØISETH UTVIKLING AS has its business address in Heimdal.

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.