BIZTRAC BETA
Civil engineering activities

HMS/SHA RÅDGIVNING AS

Org. no. 923577416 Limited company (AS) Vestby Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −136,000
Equity NOK 164,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−136k kr).

HMS/SHA RÅDGIVNING AS is registered as a limited company in Vestby, Akershus with organisation number 923577416. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “HMS/SHA rådgivning og assistanse til aktører i bygge- og anleggsbransjen. Utførelse av KP- og KU-roller ihht Byggherreforskriften.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −136,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −136,000
Equity
NOK 164,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns HMS/SHA RÅDGIVNING AS?

INGUNN HØGÅSEN
HMS/SHA RÅDGIVNING AS
NOK 2.0m rev. · NOK −136,000 profit

HMS/SHA RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HMS/SHA RÅDGIVNING AS

Who owns HMS/SHA RÅDGIVNING AS?

INGUNN HØGÅSEN is the largest registered owner, with 100.0%.

What is the revenue of HMS/SHA RÅDGIVNING AS?

HMS/SHA RÅDGIVNING AS had revenue of NOK 2.0m in 2025.

Who is the general manager of HMS/SHA RÅDGIVNING AS?

Ingunn Høgåsen is registered as general manager of HMS/SHA RÅDGIVNING AS.

Where is HMS/SHA RÅDGIVNING AS based?

HMS/SHA RÅDGIVNING AS has its business address in Son.

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.