BIZTRAC BETA
Construction of utility projects for fluids

SIGMUND HVILA AS

Org. no. 980669599 Limited company (AS) Sigdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK 215,000
Equity NOK 4.3m
Incorporated 1998
Share capital NOK 100,000

SIGMUND HVILA AS is registered as a limited company in Sigdal, Buskerud with organisation number 980669599. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet samt hva som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK 215,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK 215,000
Equity
NOK 4.3m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns SIGMUND HVILA AS?

SIGMUND HVILA
SIGMUND HVILA AS
NOK 4.0m rev. · NOK 215,000 profit

SIGMUND HVILA AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SIGMUND HVILA AS own?

SIGMUND HVILA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIGMUND HVILA AS

Who owns SIGMUND HVILA AS?

SIGMUND HVILA is the largest registered owner, with 25.0%.

What is the revenue of SIGMUND HVILA AS?

SIGMUND HVILA AS had revenue of NOK 4.0m in 2024.

Who is the general manager of SIGMUND HVILA AS?

Svein Ingar Hvila is registered as general manager of SIGMUND HVILA AS.

Where is SIGMUND HVILA AS based?

SIGMUND HVILA AS has its business address in Eggedal.

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.