BIZTRAC BETA
Uoppgitt

JOACHIM ANDERSEN HOLDING AS

Org. no. 932463458 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 12.5m
Incorporated 2023
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JOACHIM ANDERSEN HOLDING AS is registered as a limited company in Horten, Vestfold with organisation number 932463458. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Å investere i andre selskaper og virksomhet som naturlig hører sammen med dette.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 12.5m
Est. value
NOK 26.5m

Financial health · 2025

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

Who owns JOACHIM ANDERSEN HOLDING AS?

JOACHIM ANDERSEN
JOACHIM ANDERSEN HOLDING AS
· NOK −16,000 profit

JOACHIM ANDERSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOACHIM ANDERSEN HOLDING AS own?

JOACHIM ANDERSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOACHIM ANDERSEN HOLDING AS

Who owns JOACHIM ANDERSEN HOLDING AS?

JOACHIM ANDERSEN is the largest registered owner, with 100.0%.

Who is the general manager of JOACHIM ANDERSEN HOLDING AS?

Joachim Andersen is registered as general manager of JOACHIM ANDERSEN HOLDING AS.

Where is JOACHIM ANDERSEN HOLDING AS based?

JOACHIM ANDERSEN HOLDING AS has its business address in Nykirke.

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.