BIZTRAC BETA
COMPANY REGISTER PROFILE
934473329 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

JOHN-JOHNSTAD HOLDING AS

Org. no. 934473329 Limited company (AS) Lillehammer Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 210,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

JOHN-JOHNSTAD HOLDING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 934473329. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i selskaper, samt det som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −10,000
Equity
NOK 210,000
Est. value
NOK 247,000

Financial health · 2025

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

Who owns JOHN-JOHNSTAD HOLDING AS?

JOHN JOHNSTAD
JOHN-JOHNSTAD HOLDING AS
· NOK −10,000 profit

JOHN-JOHNSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOHN-JOHNSTAD HOLDING AS own?

JOHN-JOHNSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOHN-JOHNSTAD HOLDING AS

Who owns JOHN-JOHNSTAD HOLDING AS?

JOHN JOHNSTAD is the largest registered owner, with 100.0%.

Who is the general manager of JOHN-JOHNSTAD HOLDING AS?

John Johnstad is registered as general manager of JOHN-JOHNSTAD HOLDING AS.

Where is JOHN-JOHNSTAD HOLDING AS based?

JOHN-JOHNSTAD HOLDING AS has its business address in Lillehammer.

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.