BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

SMD FORVALTNING AS

Org. no. 931468715 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 12.3m
Incorporated 2023
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

SMD FORVALTNING AS is registered as a limited company in Stavanger, Rogaland with organisation number 931468715. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 1 shares. The company's stated purpose is: “Investeringer i aksjer og eiendom, og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 12.3m
Est. value
NOK 39.4m

Financial health · 2024

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

Who owns SMD FORVALTNING AS?

DANIEL BAARDSEN CHIN
SMD FORVALTNING AS
NOK 0 rev. · NOK −24,000 profit

SMD FORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMD FORVALTNING AS own?

SMD FORVALTNING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SMD FORVALTNING AS

Who owns SMD FORVALTNING AS?

DANIEL BAARDSEN CHIN is the largest registered owner, with 100.0%.

What is the revenue of SMD FORVALTNING AS?

SMD FORVALTNING AS had revenue of NOK 0 in 2024.

Where is SMD FORVALTNING AS based?

SMD FORVALTNING AS has its business address in Hafrsfjord.

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.