BIZTRAC BETA
Site preparation

SJØRHOLT INVEST AS

Org. no. 934646304 Limited company (AS) Skien Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 92,000
Incorporated 2024
Share capital NOK 120,000

Signals

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

SJØRHOLT INVEST AS is registered as a limited company in Skien, Telemark with organisation number 934646304. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 120,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 92,000
Est. value
NOK 94,000

Financial health · 2025

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

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

Who owns SJØRHOLT INVEST AS?

SINDRE SJØRHOLT
SJØRHOLT INVEST AS
NOK 0 rev. · NOK −23,000 profit

SJØRHOLT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SJØRHOLT INVEST AS own?

SJØRHOLT INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SJØRHOLT INVEST AS

Who owns SJØRHOLT INVEST AS?

SINDRE SJØRHOLT is the largest registered owner, with 100.0%.

What is the revenue of SJØRHOLT INVEST AS?

SJØRHOLT INVEST AS had revenue of NOK 0 in 2025.

Where is SJØRHOLT INVEST AS based?

SJØRHOLT INVEST AS has its business address in Skien.

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.