biztrac. BETA
COMPANY REGISTER PROFILE
826157712 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SOL INVEST AS

Org. no. 826157712 Limited company (AS) Malvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −43,000
Equity NOK 224,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SOL INVEST AS is registered as a limited company in Malvik, Trøndelag with organisation number 826157712. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og eiendom, samt hva naturlig hører til. Selskapet kan også delta i annen virksomhet gjennom kjøp av aksjer eller lignende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −43,000
▼ −111 %
Equity
NOK 224,000
▲ +847 %
Est. value
NOK 458,000

Financial health · 2025

Liquidity
2.05
Very good
Current assets ÷ current liabilities
Profitability
74.1%
Very good
Return on total assets
Solidity
65.4%
Very good
Equity as a share of total capital

Who owns SOL INVEST AS?

SOL INVEST AS
NOK 0 rev. · NOK −43,000 profit

SOL INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOL INVEST AS own?

SOL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOL INVEST AS

Who owns SOL INVEST AS?

Line Rapp Simonsen is the largest registered owner, with 50.0%.

What is the revenue of SOL INVEST AS?

SOL INVEST AS had revenue of NOK 0 in 2025.

Where is SOL INVEST AS based?

SOL INVEST AS has its business address in Hommelvik.

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.