BIZTRAC BETA
Uoppgitt

JANCO HOLDING AS

Org. no. 936731139 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −301
Equity NOK 17,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−301 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-19.

JANCO HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936731139. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, å foreta investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −301 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −301
Equity
NOK 17,000
Est. value
NOK 20,000

Financial health · 2025

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

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

Who owns JANCO HOLDING AS?

JULIUS HAVNEN ANDERSEN
JANCO HOLDING AS
NOK 0 rev. · NOK −301 profit

JANCO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JANCO HOLDING AS

Who owns JANCO HOLDING AS?

JULIUS HAVNEN ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of JANCO HOLDING AS?

JANCO HOLDING AS had revenue of NOK 0 in 2025.

Where is JANCO HOLDING AS based?

JANCO HOLDING AS has its business address in Jakobsli.

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.