BIZTRAC BETA
Rental and operating of own or leased real estate

HANSEN & ANDERSEN HOLDING AS

Org. no. 926033948 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 134,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

HANSEN & ANDERSEN HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 926033948. 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 30 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt det som naturlig hører inn under dette.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 134,000
Est. value
NOK 975,000

Financial health · 2025

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

Who owns HANSEN & ANDERSEN HOLDING AS?

AXEL ANDERSEN HOLDING AS
HANSEN & ANDERSEN HOLDING AS
· NOK −6,000 profit

HANSEN & ANDERSEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HANSEN & ANDERSEN HOLDING AS own?

HANSEN & ANDERSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HANSEN & ANDERSEN HOLDING AS

Who owns HANSEN & ANDERSEN HOLDING AS?

AXEL ANDERSEN HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of HANSEN & ANDERSEN HOLDING AS?

Aksel Einar Andersen is registered as general manager of HANSEN & ANDERSEN HOLDING AS.

Where is HANSEN & ANDERSEN HOLDING AS based?

HANSEN & ANDERSEN HOLDING AS has its business address in Drammen.

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.