biztrac. BETA
COMPANY REGISTER PROFILE
989058967 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SIHAM AS

Org. no. 989058967 Limited company (AS) Asker Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 963,000
Equity NOK 13.6m
Incorporated 2005
Share capital NOK 100,000

SIHAM AS is registered as a limited company in Asker, Akershus with organisation number 989058967. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringvirksomhet i aksjer og fast eiendom, utleie av maskiner og utstyr, samt ulike typer konsulenttjenester og landbruksvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 963,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −16 %
Operating profit
NOK 963,000
▲ +7 %
Equity
NOK 13.6m
▲ +6 %
Est. value
NOK 11.9m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
18.2%
Very good
Return on total assets
Solidity
92.3%
Very good
Equity as a share of total capital

Who owns SIHAM AS?

SIHAM AS
NOK 1.3m rev. · NOK 963,000 profit

SIHAM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIHAM AS own?

SIHAM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIHAM AS

Who owns SIHAM AS?

Sigurd Hammerstad is the largest registered owner, with 100.0%.

What is the revenue of SIHAM AS?

SIHAM AS had revenue of NOK 1.3m in 2025.

Who is the general manager of SIHAM AS?

Sigurd Hammerstad is registered as general manager of SIHAM AS.

Where is SIHAM AS based?

SIHAM AS has its business address in Røyken.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.