BIZTRAC BETA
Other captive investment companies

HAUGANS HALMSTRÅ AS

Org. no. 915810888 Limited company (AS) Hamar Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 503,000
Operating profit NOK 486,000
Equity NOK 13.2m
Incorporated 2015
Share capital NOK 30,000

HAUGANS HALMSTRÅ AS is registered as a limited company in Hamar, Innlandet with organisation number 915810888. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 503,000 in revenue and NOK 486,000 in operating profit.

Key figures · 2024

Revenue
NOK 503,000
Operating profit
NOK 486,000
Equity
NOK 13.2m
Est. value
NOK 8.7m

Financial health · 2025

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

Who owns HAUGANS HALMSTRÅ AS?

TERJE HAUGAN
HAUGANS HALMSTRÅ AS
NOK 503,000 rev. · NOK 486,000 profit

HAUGANS HALMSTRÅ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAUGANS HALMSTRÅ AS own?

HAUGANS HALMSTRÅ AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HAUGANS HALMSTRÅ AS

Who owns HAUGANS HALMSTRÅ AS?

TERJE HAUGAN is the largest registered owner, with 100.0%.

What is the revenue of HAUGANS HALMSTRÅ AS?

HAUGANS HALMSTRÅ AS had revenue of NOK 503,000 in 2024.

Where is HAUGANS HALMSTRÅ AS based?

HAUGANS HALMSTRÅ AS has its business address in Hamar.

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.