BIZTRAC BETA
Central agencies for goods and transportation procurement

GULLIKSEN HOLDING AS

Org. no. 989196006 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 14.2m
Incorporated 2005
Share capital NOK 290,000

Signals

2 flags
  • Driftsunderskudd 2024 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.

GULLIKSEN HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 989196006. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 2005. Registered share capital is NOK 290,000, divided into 3226000 shares. The company's stated purpose is: “Investerings- og holdingvirksomhet og alt som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −16,000
Equity
NOK 14.2m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns GULLIKSEN HOLDING AS?

JAN ØYVIND GULLIKSEN
GULLIKSEN HOLDING AS
· NOK −16,000 profit

GULLIKSEN HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GULLIKSEN HOLDING AS own?

GULLIKSEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GULLIKSEN HOLDING AS

Who owns GULLIKSEN HOLDING AS?

JAN ØYVIND GULLIKSEN is the largest registered owner, with 49.7%.

Who is the general manager of GULLIKSEN HOLDING AS?

Jan Øyvind Gulliksen is registered as general manager of GULLIKSEN HOLDING AS.

Where is GULLIKSEN HOLDING AS based?

GULLIKSEN 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.