BIZTRAC BETA
Masonry and bricklaying activities

SMISTAD INVEST AS

Org. no. 919116161 Limited company (AS) Karmøy Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 416,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SMISTAD INVEST AS is registered as a limited company in Karmøy, Rogaland with organisation number 919116161. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investerings- og forvaltningsvirksomhet, herunder deltakelse i andre selskaper, erverv av aksjer og andre selskapsandeler, samt all hertil hørende virksomhet.”.

Key figures · 2024

Operating profit
NOK −29,000
Equity
NOK 416,000
Est. value
NOK 5.1m

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns SMISTAD INVEST AS?

HARALD SMISTAD
SMISTAD INVEST AS
· NOK −29,000 profit

SMISTAD INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SMISTAD INVEST AS own?

SMISTAD INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SMISTAD INVEST AS

Who owns SMISTAD INVEST AS?

HARALD SMISTAD is the largest registered owner, with 50.0%.

Who is the general manager of SMISTAD INVEST AS?

Harald Smistad is registered as general manager of SMISTAD INVEST AS.

Where is SMISTAD INVEST AS based?

SMISTAD INVEST AS has its business address in Karmsund.

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.