BIZTRAC BETA
Other support activities to arts and performing arts

FISKEPIREN AS

Org. no. 927608413 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 27.8m
Operating profit NOK −5.2m
Equity NOK −1.6m
Incorporated 2021
Employees 62
Share capital NOK 2.1m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,2 mill kr).

FISKEPIREN AS is registered as a limited company in Stavanger, Rogaland with organisation number 927608413. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2021 and has 62 registered employees. Registered share capital is NOK 2.1m, divided into 2149987 shares. The company's stated purpose is: “Tilrettelegging for og produksjon av konserter og kulturelle aktiviteter samt drift av restauranter og kafeer.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.8m in revenue and NOK −5.2m in operating profit.

Key figures · 2024

Revenue
NOK 27.8m
Operating profit
NOK −5.2m
Equity
NOK −1.6m

Financial health · 2024

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

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

Who owns FISKEPIREN AS?

SKY HOLDING AS
FISKEPIREN AS
NOK 27.8m rev. · NOK −5.2m profit

FISKEPIREN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISKEPIREN AS

Who owns FISKEPIREN AS?

SKY HOLDING AS is the largest registered owner, with 47.2%.

What is the revenue of FISKEPIREN AS?

FISKEPIREN AS had revenue of NOK 27.8m in 2024.

Where is FISKEPIREN AS based?

FISKEPIREN 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.