BIZTRAC BETA
Rental and operating of own or leased real estate

JON SKINSTAD HOLDING AS

Org. no. 825803262 Limited company (AS) Nord-Odal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 1.8m
Incorporated 2020
Share capital NOK 30,000

Signals

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

JON SKINSTAD HOLDING AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 825803262. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 1.8m
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.8%
Satisfactory
Equity as a share of total capital

Who owns JON SKINSTAD HOLDING AS?

JON KRISTOFER SKINSTAD
JON SKINSTAD HOLDING AS
NOK 0 rev. · NOK −5,000 profit

JON SKINSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JON SKINSTAD HOLDING AS own?

JON SKINSTAD HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about JON SKINSTAD HOLDING AS

Who owns JON SKINSTAD HOLDING AS?

JON KRISTOFER SKINSTAD is the largest registered owner, with 100.0%.

What is the revenue of JON SKINSTAD HOLDING AS?

JON SKINSTAD HOLDING AS had revenue of NOK 0 in 2025.

Where is JON SKINSTAD HOLDING AS based?

JON SKINSTAD HOLDING AS has its business address in Sagstua.

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.