BIZTRAC BETA
Photographic activities

CORONABERGET AS

Org. no. 923875506 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 17,000
Operating profit NOK −19,000
Equity NOK 23,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

CORONABERGET AS is registered as a limited company in Stavanger, Rogaland with organisation number 923875506. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Sagbrukproduksjon og salg av varer og tjenester. Fotograf og salg av fotografier og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 17,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 17,000
Operating profit
NOK −19,000
Equity
NOK 23,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns CORONABERGET AS?

THOMAS PERRY TORGERSEN GISKE
CORONABERGET AS
NOK 17,000 rev. · NOK −19,000 profit

CORONABERGET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CORONABERGET AS

Who owns CORONABERGET AS?

THOMAS PERRY TORGERSEN GISKE is the largest registered owner, with 100.0%.

What is the revenue of CORONABERGET AS?

CORONABERGET AS had revenue of NOK 17,000 in 2025.

Who is the general manager of CORONABERGET AS?

Thomas Perry Torgersen Giske is registered as general manager of CORONABERGET AS.

Where is CORONABERGET AS based?

CORONABERGET AS has its business address in Stavanger.

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.