BIZTRAC BETA
Uoppgitt

J HERMANSEN HOLDING AS

Org. no. 933774481 Limited company (AS) Ål Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

J HERMANSEN HOLDING AS is registered as a limited company in Ål, Buskerud with organisation number 933774481. 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: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns J HERMANSEN HOLDING AS?

JØRGEN SÆTHER HERMANSEN
J HERMANSEN HOLDING AS
NOK 0 rev. · NOK 0 profit

J HERMANSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J HERMANSEN HOLDING AS own?

J HERMANSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about J HERMANSEN HOLDING AS

Who owns J HERMANSEN HOLDING AS?

JØRGEN SÆTHER HERMANSEN is the largest registered owner, with 100.0%.

What is the revenue of J HERMANSEN HOLDING AS?

J HERMANSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is J HERMANSEN HOLDING AS based?

J HERMANSEN HOLDING AS has its business address in Torpo.

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.