BIZTRAC BETA
Retail sale of other new goods

GULSKOGEN FOTO AS

Org. no. 927120003 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 252,000
Operating profit NOK −2.4m
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,4 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GULSKOGEN FOTO AS is registered as a limited company in Drammen, Buskerud with organisation number 927120003. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av fotobutikk og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 252,000 in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 252,000
Operating profit
NOK −2.4m
Equity
NOK 30,000
Est. value
NOK 38,000

Financial health · 2024

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

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

Who owns GULSKOGEN FOTO AS?

ELITE FOTO AS
GULSKOGEN FOTO AS
NOK 252,000 rev. · NOK −2.4m profit

GULSKOGEN FOTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULSKOGEN FOTO AS

Who owns GULSKOGEN FOTO AS?

ELITE FOTO AS is the largest registered owner, with 100.0%.

What is the revenue of GULSKOGEN FOTO AS?

GULSKOGEN FOTO AS had revenue of NOK 252,000 in 2024.

Where is GULSKOGEN FOTO AS based?

GULSKOGEN FOTO AS has its business address in Drammen.

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.