BIZTRAC BETA
Uoppgitt

GIEBNIE HOLDING AS

Org. no. 926858572 Limited company (AS) Stjørdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK −23,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−23k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

GIEBNIE HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 926858572. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskap, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −23,000

Financial health · 2024

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GIEBNIE HOLDING AS?

Øyvind Haugan
GIEBNIE HOLDING AS
NOK 0 rev. · NOK −9,000 profit

GIEBNIE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GIEBNIE HOLDING AS own?

GIEBNIE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GIEBNIE HOLDING AS

Who owns GIEBNIE HOLDING AS?

Øyvind Haugan is the largest registered owner, with 100.0%.

What is the revenue of GIEBNIE HOLDING AS?

GIEBNIE HOLDING AS had revenue of NOK 0 in 2024.

Where is GIEBNIE HOLDING AS based?

GIEBNIE HOLDING AS has its business address in Stjørdal.

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.