BIZTRAC BETA
COMPANY REGISTER PROFILE
928721841 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SMARTINVEST AS

Org. no. 928721841 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 24,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

SMARTINVEST AS is registered as a limited company in Bergen, Vestland with organisation number 928721841. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SMARTINVEST AS?

SMARTINVEST AS
· NOK −2,000 profit

SMARTINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SMARTINVEST AS own?

SMARTINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SMARTINVEST AS

Who owns SMARTINVEST AS?

MARTIN HAGEN MYRESTRAND is the largest registered owner, with 100.0%.

Who is the general manager of SMARTINVEST AS?

Martin Hagen Myrestrand is registered as general manager of SMARTINVEST AS.

Where is SMARTINVEST AS based?

SMARTINVEST AS has its business address in Bergen.

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

Report a problem

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