BIZTRAC BETA
Uoppgitt

FULL GNU HOLDING AS

Org. no. 931007300 Limited company (AS) Lindesnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 51,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

FULL GNU HOLDING AS is registered as a limited company in Lindesnes, Agder with organisation number 931007300. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 51,000
Est. value
NOK 60,000

Financial health · 2025

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

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

Who owns FULL GNU HOLDING AS?

No shareholders are registered for FULL GNU HOLDING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FULL GNU HOLDING AS own?

FULL GNU HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FULL GNU HOLDING AS

What is the revenue of FULL GNU HOLDING AS?

FULL GNU HOLDING AS had revenue of NOK 0 in 2025.

Where is FULL GNU HOLDING AS based?

FULL GNU HOLDING AS has its business address in Marnardal.

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.