BIZTRAC BETA
Beverage serving activities

GUL SNØ AS

Org. no. 927613026 Limited company (AS) Fredrikstad Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK −3,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

GUL SNØ AS is registered as a limited company in Fredrikstad, Østfold with organisation number 927613026. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Salg av mat, drikke og andre produkter i samme bransje. Investering i og utvikling av aksjeportefølje, selskaper innen ulike bransjer, formues og finansielle produkter og dertilhørende tjenester, men ikke begrenset til kun dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK −3,000

Financial health · 2024

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

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

Who owns GUL SNØ AS?

PAAL ENGELHARDT NYGÅRD
GUL SNØ AS
NOK 0 rev. · NOK −14,000 profit

GUL SNØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUL SNØ AS

Who owns GUL SNØ AS?

PAAL ENGELHARDT NYGÅRD is the largest registered owner, with 50.0%.

What is the revenue of GUL SNØ AS?

GUL SNØ AS had revenue of NOK 0 in 2024.

Where is GUL SNØ AS based?

GUL SNØ AS has its business address in Sellebakk.

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.