BIZTRAC BETA
Uoppgitt

BT HANSEN HOLDING AS

Org. no. 932482797 Limited company (AS) Klepp Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK 13,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

BT HANSEN HOLDING AS is registered as a limited company in Klepp, Rogaland with organisation number 932482797. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Deltakelse i annen virksomhet ved erverv av aksjer, samt alt som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 13,000
Est. value
NOK 15,000

Financial health · 2024

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

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

Who owns BT HANSEN HOLDING AS?

BJARNE TOFTDAL HANSEN
BT HANSEN HOLDING AS
NOK 0 rev. · NOK −7,000 profit

BT HANSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BT HANSEN HOLDING AS own?

BT HANSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BT HANSEN HOLDING AS

Who owns BT HANSEN HOLDING AS?

BJARNE TOFTDAL HANSEN is the largest registered owner, with 100.0%.

What is the revenue of BT HANSEN HOLDING AS?

BT HANSEN HOLDING AS had revenue of NOK 0 in 2024.

Where is BT HANSEN HOLDING AS based?

BT HANSEN HOLDING AS has its business address in Klepp Stasjon.

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.