BIZTRAC BETA
Rental and operating of own or leased real estate

SJN HOLDING AS

Org. no. 929654048 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −30,000
Equity NOK 729,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SJN HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 929654048. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i andre selskaper. Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 729,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns SJN HOLDING AS?

SONDRE ALEXANDER JUUL NILSEN
SJN HOLDING AS
NOK 0 rev. · NOK −30,000 profit

SJN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SJN HOLDING AS own?

SJN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SJN HOLDING AS

Who owns SJN HOLDING AS?

SONDRE ALEXANDER JUUL NILSEN is the largest registered owner, with 100.0%.

What is the revenue of SJN HOLDING AS?

SJN HOLDING AS had revenue of NOK 0 in 2025.

Where is SJN HOLDING AS based?

SJN HOLDING 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.