biztrac. BETA
COMPANY REGISTER PROFILE
995323818 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of metal structures and parts of structures

SMIHUSET AS

Org. no. 995323818 Limited company (AS) Bergen Incorporated 2010 Active
Revenue 2025 NOK 38.7m
Operating profit NOK 248,000
Equity NOK 8.4m
Incorporated 2010
Employees 17
Share capital NOK 100,000

SMIHUSET AS is registered as a limited company in Bergen, Vestland with organisation number 995323818. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2010 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er produksjon/ salg av bygningsartikler av metall og dertil tilhørende virksomhet. Investering i aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 38.7m in revenue and NOK 248,000 in operating profit.

Key figures · 2025

Revenue
NOK 38.7m
▲ +9 %
Operating profit
NOK 248,000
▼ −85 %
Equity
NOK 8.4m
▼ −0 %
Est. value
NOK 5.9m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
2.1%
Weak
Return on total assets
Solidity
61.3%
Very good
Equity as a share of total capital

Who owns SMIHUSET AS?

SMIHUSET AS
NOK 38.7m rev. · NOK 248,000 profit

SMIHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMIHUSET AS

Who owns SMIHUSET AS?

SMIHUSET EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SMIHUSET AS?

SMIHUSET AS had revenue of NOK 38.7m in 2025.

Who is the general manager of SMIHUSET AS?

Roy Sathasivam Ragunathan Kengakaran is registered as general manager of SMIHUSET AS.

Where is SMIHUSET AS based?

SMIHUSET AS has its business address in Haukeland.

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.