BIZTRAC BETA
Other health services

GIDAZ AS

Org. no. 986097872 Limited company (AS) Øksnes Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 448,000
Operating profit NOK −14,000
Equity NOK 68,000
Incorporated 2003
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

GIDAZ AS is registered as a limited company in Øksnes, Nordland with organisation number 986097872. The business is classified under other health services (NACE 86.993). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av helsetjenester og andre produkter/tjenester som naturlig hører sammen med dette. Delta i andre selskap, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 448,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 448,000
Operating profit
NOK −14,000
Equity
NOK 68,000
Est. value
NOK 340,000

Financial health · 2024

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

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

Who owns GIDAZ AS?

ERIK INGVAR ZADIG
GIDAZ AS
NOK 448,000 rev. · NOK −14,000 profit

GIDAZ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIDAZ AS

Who owns GIDAZ AS?

ERIK INGVAR ZADIG is the largest registered owner, with 100.0%.

What is the revenue of GIDAZ AS?

GIDAZ AS had revenue of NOK 448,000 in 2024.

Who is the general manager of GIDAZ AS?

Mai Lise Karlsen Zadig is registered as general manager of GIDAZ AS.

Where is GIDAZ AS based?

GIDAZ AS has its business address in Alsvåg.

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.