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

SOLBU TORP AS

Org. no. 829360292 Limited company (AS) Folldal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SOLBU TORP AS is registered as a limited company in Folldal, Innlandet with organisation number 829360292. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre eierandeler, samt tilsvarende og annen type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
▲ +79 %
Equity
NOK 15,000
▼ −10 %
Est. value
NOK 18,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

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

Who owns SOLBU TORP AS?

SOLBU TORP AS
NOK 0 rev. · NOK −2,000 profit

SOLBU TORP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLBU TORP AS own?

SOLBU TORP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SOLBU TORP AS

Who owns SOLBU TORP AS?

Reidar Odden is the largest registered owner, with 100.0%.

What is the revenue of SOLBU TORP AS?

SOLBU TORP AS had revenue of NOK 0 in 2025.

Where is SOLBU TORP AS based?

SOLBU TORP AS has its business address in Folldal.

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.