BIZTRAC BETA
Rental and operating of own or leased real estate

ISW HAUGE AS

Org. no. 919496304 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 320,000
Operating profit NOK 10,000
Equity NOK 39,000
Incorporated 2017
Share capital NOK 30,000

ISW HAUGE AS is registered as a limited company in Oslo, Oslo with organisation number 919496304. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i fast eiendom og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 320,000 in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 320,000
Operating profit
NOK 10,000
Equity
NOK 39,000
Est. value
NOK 53,000

Financial health · 2025

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

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

Who owns ISW HAUGE AS?

KRISTIAN HAUGE AS
ISW HAUGE AS
NOK 320,000 rev. · NOK 10,000 profit

ISW HAUGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ISW HAUGE AS er morselskap for 8 datterselskaper:

Frequently asked questions about ISW HAUGE AS

Who owns ISW HAUGE AS?

KRISTIAN HAUGE AS is the largest registered owner, with 100.0%.

What is the revenue of ISW HAUGE AS?

ISW HAUGE AS had revenue of NOK 320,000 in 2025.

Who is the general manager of ISW HAUGE AS?

Kristian Hauge is registered as general manager of ISW HAUGE AS.

Where is ISW HAUGE AS based?

ISW HAUGE AS has its business address in Oslo.

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.