biztrac. BETA
COMPANY REGISTER PROFILE
821966302 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BENDIKSEN HOLDING AS

Org. no. 821966302 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −159,000
Equity NOK 99.0m
Incorporated 2018
Share capital NOK 60,000

Signals

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

BENDIKSEN HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 821966302. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Eie aksjer i datterselskap, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −159,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −159,000
▼ −28 %
Equity
NOK 99.0m
▲ +4 %
Est. value
NOK 94.5m

Financial health · 2025

Liquidity
5.65
Very good
Current assets ÷ current liabilities
Profitability
7.4%
Satisfactory
Return on total assets
Solidity
96.8%
Very good
Equity as a share of total capital

Who owns BENDIKSEN HOLDING AS?

BENDIKSEN HOLDING AS
NOK 0 rev. · NOK −159,000 profit

BENDIKSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BENDIKSEN HOLDING AS own?

BENDIKSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BENDIKSEN HOLDING AS

Who owns BENDIKSEN HOLDING AS?

Pål Birger Bendiksen is the largest registered owner, with 100.0%.

What is the revenue of BENDIKSEN HOLDING AS?

BENDIKSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is BENDIKSEN HOLDING AS based?

BENDIKSEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.