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

GIKA HOLDING AS

Org. no. 989218263 Limited company (AS) Notodden Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −182,000
Equity NOK 11.1m
Incorporated 2005
Share capital NOK 3.6m

Signals

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

GIKA HOLDING AS is registered as a limited company in Notodden, Telemark with organisation number 989218263. 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 3.6m, divided into 3636220 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, kjøp og salg av aksjer og andre verdipapirer, samt kjøp, salg og utleie av fast eiendom, samt virksomhet som naturlig faller innunder dette.”.

Key figures · 2025

Operating profit
NOK −182,000
▼ −325 %
Equity
NOK 11.1m
▼ −22 %
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns GIKA HOLDING AS?

GIKA HOLDING AS
· NOK −182,000 profit

GIKA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GIKA HOLDING AS own?

GIKA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GIKA HOLDING AS

Who owns GIKA HOLDING AS?

Gisle Moen is the largest registered owner, with 50.0%.

Who is the general manager of GIKA HOLDING AS?

Gisle Moen is registered as general manager of GIKA HOLDING AS.

Where is GIKA HOLDING AS based?

GIKA HOLDING AS has its business address in Notodden.

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.