biztrac. BETA
COMPANY REGISTER PROFILE
889126442 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of furniture, including mattresses and box springs

GULLAKSEN HOLDING AS

Org. no. 889126442 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 653,000
Incorporated 2005
Share capital NOK 400,000

Signals

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

GULLAKSEN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 889126442. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Selskapets virksomhet er investeringer og alt som dermed står i forbindelse, samt deltakelse som aksjonær eller på annen måte i andre foretak.”.

Key figures · 2025

Operating profit
NOK −38,000
▼ −12 %
Equity
NOK 653,000
▼ −6 %
Est. value
NOK 816,000

Financial health · 2025

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

Who owns GULLAKSEN HOLDING AS?

GULLAKSEN HOLDING AS
· NOK −38,000 profit

GULLAKSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULLAKSEN HOLDING AS own?

GULLAKSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

GULLAKSEN HOLDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about GULLAKSEN HOLDING AS

Who owns GULLAKSEN HOLDING AS?

Sigurd Gullaksen is the largest registered owner, with 100.0%.

Where is GULLAKSEN HOLDING AS based?

GULLAKSEN HOLDING AS has its business address in Trondheim.

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.